CVE-2026-58301: When Apache Shiro is used with the Jakarta EE integration module, a low-privileged user can craft an HTTP requ

Routine

MEDIUM 6.5WATCHLISTUPGRADE

CVE-2026-58301 is a medium-severity flaw (CVSS 6.5) affecting shiro. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

When Apache Shiro is used with the Jakarta EE integration module, a low-privileged user can craft an HTTP request that causes the server to initiate a connection to an attacker-controlled URL and transmit attacker-controlled data. This vulnerability affects Apache Shiro versions 2.x through 3.0.0 only in deployments that use the Jakarta EE integration module. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue. + Alternatively,

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 60%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-08-31
Last modified	2026-09-01

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-31 08:17 UTCPublished CVE record published
2026-09-01 18:06 UTCUpdated Record last modified

apache shiro UPGRADE

Affected: >= 2.0.0 and < 3.0.1

Fixed in: 3.0.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy shiro || rpm -q shiro || shiro --version

2. UPGRADE to 3.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade shiro

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade shiro

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison shiro sudo apt install shiro=<VERSION_BEFORE_2.0.0> sudo apt-mark hold shiro

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list shiro sudo dnf downgrade shiro-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add shiro

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-58301?

shiro: upgrade to 3.0.1. Exact commands for each OS are on this page.

Is CVE-2026-58301 being exploited?

CVE-2026-58301 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-58301 affect?

CVE-2026-58301 affects shiro. Severity is medium (CVSS 6.5). When Apache Shiro is used with the Jakarta EE integration module, a low-privileged user can craft an HTTP request that causes the server to initiate a connection to an attacker-controlled URL and transmit attacker-controlled data. This vuln

How urgent is CVE-2026-58301?

Priority 38/100. On your watchlist

Related CVEs

CVE-2026-49268 CRITICAL 9.1 UPGRADE A remote attacker can inject LDAP special characters into the Distinguished Name (DN) construction in DefaultL

References

← Back to latest CVEs