CVE-2026-129348: Shiro · When PropertiesRealm reloads its properties file, removed users and narrowed permissions
Affects shiroSource GCVE Database
Not known to be exploited · CVSS 2.3 Low · fixed in 3.0.2 : update shiro when convenient.
Data as of 18 Nov 2026, 15:49 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10shiropkg:deb/ubuntu/shiro?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSshiropkg:deb/ubuntu/shiro?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSshiropkg:deb/ubuntu/shiro?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSshiropkg:deb/ubuntu/shiro?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSshiropkg:deb/ubuntu/shiro?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSshiropkg:deb/ubuntu/shiro?arch=source&distro=esm-apps/bionicOther 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. If upgrading is not immediately possible, restart the application after removing users or narrowing permissions to ensure changes take effect.
Description
Apache Shiro versions through 3.0.1 have a vulnerability in the PropertiesRealm component where reloading the properties file does not properly remove users or narrow permissions. This can cause removed users and restricted permissions to remain effective until the application is restarted. The issue is fixed in version 3.0.2 and later.