CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- Fixed in 3.0.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Apache Shiro versions through 3.0.0 (shiro-core before 3.0.1) Uses DefaultLdapRealm or JndiLdapRealm authenticationCachingEnabled set to true on the LDAP realm
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.60% · 48th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
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.
Original 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.
Who should check
Teams running Apache Shiro through 3.0.0 with DefaultLdapRealm or JndiLdapRealm and authenticationCachingEnabled set to true
“Apache Shiro (org.apache.shiro:shiro-core) before 3.0.1”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Maven packages
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Apache Shiro versions through 3.0.0 (shiro-core before 3.0.1) Uses DefaultLdapRealm or JndiLdapRealm authenticationCachingEnabled set to true on the LDAP realmUpgrade to a fixed version: 3.0.1.
Workaround: Disable authentication caching on the LDAP realm (the default), or configure a credentials matcher such as SimpleCredentialsMatcher.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Public exploit activity
- GitHub PoC repos: 1
- Posted on X by cve.now Nov 15
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
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.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Write-ups · 1
Establishes: Technical detail and context.
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129349
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: cve.now feed data
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: openwall.com
Which versions are affected by CVE-2026-129349?
org.apache.shiro:shiro-core (Maven): before 3.0.1.Source: cve.now feed data
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: openwall.com
How do I fix CVE-2026-129349?
Upgrade to Apache Shiro 3.0.1 or later, which fixes the issue.Source: openwall.com