Loading story…
Apache disclosed CVE-2026-105869, a critical Apache Pulsar authorization bypass rated 9.2 under CVSS 4.0, that can let unauthenticated clients obtain arbitrary roles, including superuser privileges. The flaw affects deployments using MultiRolesTokenAuthorizationProvider with a non-empty anonymousUserRole setting. When failed HTTP authentication falls back to the anonymous role, the authorization provider trusts role claims from forged or unsigned JWTs retained in request headers without verifying their signatures. Eligible broker HTTP and WebSocket requests are affected; Pulsar binary-protocol connections are not.
Affected releases span 2.8.1 through versions before 4.0.14, and 4.1.0 through versions before 4.2.5. Administrators should upgrade to the applicable patched release, 4.0.14 or 4.2.5, or newer. Where upgrades are not immediately possible, Apache recommends removing anonymousUserRole from broker and WebSocket service configurations or restricting access to those HTTP endpoints to trusted clients. Security teams should prioritize deployments combining the affected authorization provider, anonymous-role fallback, and externally reachable HTTP or WebSocket endpoints.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
The Apache Pulsar PMC published a combined announcement covering 14 vulnerabilities, including the previously documented critical JWT bypass and 13 additional flaws enabling cross-tenant access, message deletion, unauthorized publishing, and security-control bypasses. Apache stated that all 14 are fixed in versions 4.0.14, 4.2.5, and 5.0.0 and recommended upgrading.
Patched releases obtain authorization roles only from verified tokens and prevent invalid tokens from supplying additional privileges through anonymous fallback. Apache advised upgrading to the applicable patched release or newer; interim mitigations include removing anonymousUserRole or restricting HTTP endpoints to trusted clients.
Apache disclosed CVE-2026-105869, a CVSS 4.0 9.2 vulnerability found by George Chen. Unauthenticated attackers can use forged JWT role claims to gain arbitrary privileges, including super-user access, on eligible HTTP and WebSocket requests when MultiRolesTokenAuthorizationProvider and anonymous-role fallback are configured.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourcelists.apache.org
Open sourcepulsar.apache.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Apache disclosed **CVE-2026-105944**, a critical authentication and authorization vulnerability affecting every Apache Pulsar Manager release, versions 0.1.0 through 0.4.0. Rated **CVSS 4.0 10.0**, the flaw allows unauthenticated attackers with network access to abuse proxied Pulsar administration requests and steal configured HTTP authentication credentials. In versions 0.3.0 and later, attackers can also create administrator accounts after initialization and take full control of Pulsar Manager, an administration interface for Apache Pulsar. **Pulsar Manager has been retired, is unsupported, and will receive no fixes.** Apache advises users to remove deployments and migrate to an alternative administration interface. Until removal, organizations should restrict access to trusted administrators and assess whether exposed credentials or token-signing keys need replacement. The advisory concerns Pulsar Manager; it does not establish that all Apache Pulsar deployments are affected.
Oct 21, 2026
Apache Syncope disclosed three vulnerabilities in its identity-management platform that can allow authorized administrators with applicable entitlements to manipulate backend databases through SQL injection, bypass the Groovy sandbox to execute code in the application context, or reuse JWT access tokens to impersonate more privileged users. Affected versions span the 3.0, 4.0, and 4.1 release branches, including 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2, depending on the vulnerable component. Organizations should upgrade to Apache Syncope **4.0.8** or **4.1.3**, review privileged-user and REST API activity, and investigate anomalous Task-search queries or other suspicious database behavior. Administrators should also rotate potentially exposed JWTs to reduce the risk of token reuse and privilege impersonation.
Sep 16, 2026
Apache disclosed **CVE-2026-43512**, a moderate-severity authentication bypass in Tomcat's DIGEST authenticator that can let any user unknown to the configured Realm authenticate if the supplied password is `"null"`. The flaw affects multiple supported branches, including Tomcat `11.0.0-M1` through `11.0.21`, `10.1.0-M1` through `10.1.54`, and `9.0.0.M1` through `9.0.117`, with older unsupported releases potentially affected. Apache advised users to upgrade to `11.0.22+`, `10.1.55+`, or `9.0.118+`. Apache also disclosed **CVE-2026-44417**, a moderate-severity flaw in the JMS transport component of Apache CXF caused by an incomplete fix for **CVE-2025-48913**. The remaining vulnerable code path can still lead to remote code execution when untrusted users are allowed to configure JMS. Affected releases include CXF JMS transport `4.2.0` before `4.2.1`, `4.0.0` before `4.1.6`, and all `3.6.x` versions before `3.6.11`; Apache said organizations should upgrade to `4.2.1`, `4.1.6`, or `3.6.11`.
May 25, 2026