# CVE-2026-129348: Apache Shiro: PropertiesRealm reload does not remove deleted users or narrowed permissions

> Removed users or narrowed permissions may persist after Shiro PropertiesRealm reloads, affecting apps using that realm.

- **Severity:** Low 2.3 (`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:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`PropertiesRealm`)
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129348, GHSA-p746-782w-8465, UBUNTU-CVE-2026-129348

## What is CVE-2026-129348?

CVE-2026-129348 is a low-severity privilege escalation vulnerability in Apache Shiro, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When PropertiesRealm reloads its properties file, removed users and narrowed permissions could remain in effect.
This issue affects all Apache Shiro versions through 3.0.1, only when PropertiesRealm`loads its properties from a file, which is reloaded periodically by default.

Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue.
Alternatively, restart the application after removing users or narrowing permissions.

Weakness: CWE-269 (Improper Privilege Management)

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

1 open source package ship an affected version, including org.apache.shiro:shiro-core.

An affected version is only exploitable if your software calls PropertiesRealm. Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `org.apache.shiro:shiro-core` | Maven | `pkg:maven/org.apache.shiro/shiro-core` | All versions | 3.0.2 |

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

Upgrade org.apache.shiro:shiro-core to 3.0.2 or later.

## Is CVE-2026-129348 being exploited?

There is no known exploitation of CVE-2026-129348 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129348 and fix it if it is affected.

What it is: CVE-2026-129348 is a low-severity privilege escalation vulnerability in Apache Shiro, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129348 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls PropertiesRealm. Many projects that include it are not exposed.

Affected packages and fixed versions:
- org.apache.shiro:shiro-core (Maven): affected all versions; fixed in 3.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to PropertiesRealm and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129348/ (Markdown: https://insights.sbomify.com/CVE-2026-129348/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129348
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129348
- OSV: https://osv.dev/vulnerability/CVE-2026-129348

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129348/
Summaries are generated and may contain mistakes; the official description above is the record.
