CVE-2026-129348: Apache Shiro · Improper Privilege Management
Affects Apache ShiroSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 3.0.2 when convenient.
Data as of 16 Nov 2026, 14:06 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 3.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/V:D/RE:L/U:GreenExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Apache Shiro and org.apache.shiro/shiro-core to 3.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Shiroorg.apache.shiro:shiro-core | Affected
| Fixed in
|
Mavenorg.apache.shiro/shiro-corepkg:maven/org.apache.shiro/shiro-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Shiro to version 3.0.2 or later, which contains the official fix for this issue. Alternatively, restart the application after removing users or narrowing permissions to ensure changes take effect. No other mitigation is required.
Description
Apache Shiro versions up to 3.0.1 have an improper privilege management vulnerability in the PropertiesRealm component. When the properties file is reloaded periodically, removed users and narrowed permissions may still remain effective, potentially allowing unauthorized access. This issue is fixed in version 3.0.2. Users should upgrade to 3.0.2 or later or restart the application after modifying user permissions.