The Exploit Bulletin

Archives
Log in
Subscribe
November 13, 2026

The Exploit Bulletin — Friday, November 13, 2026: 3 issues require action

Friday, November 13, 2026 — 3 issues require action. If you run none of the software below, you are done.

Affects: Apache Axis · MantisBT · ConnectWise ScreenConnect


1. Unauthenticated SOAP fault class instantiation leads to remote code execution in Apache Axis 1.x (CVE-2026-90436)

REMOTE CODE EXECUTION · CRITICAL · CVSS 9.8

VulnCheck added this flaw to its known-exploited catalog on 2026-11-12 alongside a public exploit in XDB, and The Hacker News reports the first documented exploitation attempts against it, so any application still embedding the end-of-life Axis 1.x runtime is reachable by an unauthenticated attacker who can execute code on the server.

When Apache Axis 1.x parses an inbound SOAP Fault that names a class, it loads that class (running its static initializer) and, if a String detail is also present, instantiates it through its String constructor before verifying it is an AxisFault. The fault is processed while the engine is still resolving the target service, before any per-service handler chain or authentication runs, so with a suitable class on the application's classpath an unauthenticated remote attacker achieves code execution.

Affected: Apache Axis 1.x up to and including 1.4 (end-of-life); Apache Axis 1.x source builds from commit aac718c6035435d96b39d6aebb9c078a13af7cc8 prior to fix commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd

How to Test: Inventory your Java applications and vendor products for a bundled Apache Axis 1.x runtime (axis-rt-core / org.apache.axis classes); any Axis 1.x build up to 1.4, or a source build older than commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd, is affected. Compare your SOAPFaultBuilder.createFault() against the fix: patched code only constructs the fault class when AxisFault.class.isAssignableFrom(faultClass). To look for attempts, review web server and application access logs for unsolicited POSTs to Axis SOAP endpoints whose bodies carry a SOAP Fault naming a Java class together with a String detail, and check the Java process for unexpected child processes, class loading, or outbound connections.

How to Mitigate: Apache Axis 1.x is end-of-life and no fixed release has been published. Rebuild the Axis 1.x runtime from the apache/axis-axis1-java repository at or after commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd, which restricts reflective fault construction to genuine AxisFault subtypes, and redeploy the affected applications. Where rebuilding is not possible today, remove or firewall the Axis 1.x SOAP endpoints from untrusted networks, and ask vendors of products that embed Axis 1.x for a build containing this fix.

Evidence: VulnCheck KEV · The Hacker News: first documented exploitation attempts aimed at CVE-2026-90436 · VulnCheck XDB public exploit

Full entry with sources →


2. SOAP API password type-juggling authentication bypass in MantisBT on MySQL (CVE-2026-30849)

AUTHENTICATION BYPASS · CRITICAL · CVSS 9.3

VulnCheck's canary sensors observed exploitation attempts on 2026-11-12 and a working exploit is in VulnCheck XDB, so an exposed MantisBT instance on MySQL with the SOAP API enabled can have any known account, including administrators, taken over without a password.

MantisBT's SOAP API does not type-check the password parameter, and on MySQL-family databases the implicit string-to-integer conversion lets a crafted SOAP envelope log in as any user whose username is known, without the password, and call every API function that account can use. Installs on other database backends are not affected.

Affected: MantisBT < 2.28.1 (on MySQL/MariaDB database backends)

How to Test: Check the MantisBT version from the admin interface; any build below 2.28.1 running on a MySQL-family database is affected, while other database backends are not. Review web server logs for SOAP API requests from unexpected sources and audit recent logins, API activity and account changes that users did not initiate, especially on administrator accounts; the GitHub advisory GHSA-phrq-pc6r-f6gh and fix commit b349e5c890eeda9bd82e7c7e14479853f8a30d9f show the exact code change to verify against.

How to Patch: Upgrade to MantisBT 2.28.1 or later. If the upgrade must wait, disable the SOAP API or restrict network access to it until patched.

Evidence: VulnCheck KEV · VulnCheck XDB public exploit

Full entry with sources →


3. ScreenConnect cloud panels abused via third-party extensions to backdoor MSP clients

CONFIRMED BREACH · CRITICAL

Attackers pushed rogue clients and the self-spreading SCKit backdoor to 288 hosts in 90 minutes on 11 November, and it waits for technicians to connect so it can spread to every other client they manage.

Attackers abused unauthorized access to cloud-hosted ScreenConnect panels, likely via third-party extensions, to run commands on managed endpoints, compromising at least 6 MSPs and 288 hosts across 48 organizations. They deployed rogue ScreenConnect clients and the SCKit backdoor, which steals session cookies and spreads to technician workstations. ConnectWise disabled five third-party extensions across about 400 partner environments.

Affected: ConnectWise ScreenConnect cloud-hosted instances with third-party extensions installed

How to Test: Check ConnectWise's advisory for whether your instance had one of the five disabled extensions; review ScreenConnect audit logs for commands run on 11 November; hunt endpoints and technician workstations for unexpected ScreenConnect client installations and SCKit persistence.

How to Mitigate: Keep the flagged extensions removed, uninstall rogue ScreenConnect clients, reimage hosts with SCKit, rotate ScreenConnect and technician credentials and invalidate sessions, and enforce MFA on panels.

Evidence: The Hacker News: ScreenConnect attacks target 288 endpoints across 48 organizations · SecurityWeek: Hackers deploy malware in fresh ScreenConnect campaign

Full entry with sources →


Read on the web · Every past edition

The Exploit Bulletin is free and daily. It publishes only what security teams must act on today — nothing else. Forward it freely.

Spot an error, or an exploit we missed? Reply here or email [email protected].

Don't miss what's next. Subscribe to The Exploit Bulletin:
← Newer The Exploit Bulletin — Saturday, November 14, 2026: 3 issues require action Older → The Exploit Bulletin — Thursday, November 12, 2026: 4 issues require action
www.exploitbulletin.com
jbac.co
LinkedIn
Powered by Buttondown, the easiest way to start and grow your newsletter.