Quick answers
- Is CVE-2026-58301 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58301 being exploited in the wild.
- How severe is CVE-2026-58301?
- Medium severity, with a CVSS score of 6.5, published 31 August 2026.
- Which products and versions are affected?
- Apache Shiro 2.x through 3.0.0.
- Is there a fix for CVE-2026-58301?
- A patch was published on 2026-08-31: Fixed in version 3.0.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58301 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-58301?
- Check whether you run Apache Shiro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a Server-Side Request Forgery (SSRF) in Apache Shiro's Jakarta EE integration module. A low-privileged user can craft a malicious HTTP request that forces the server to initiate an outbound connection to an attacker-controlled URL and transmit attacker-controlled data. The attack is specific to deployments using the Jakarta EE integration module and affects Shiro versions 2.x through 3.0.0. The vulnerability was patched in version 3.0.1, or can be mitigated by configuring the `org.apache.shiro.form-resubmit-host` and `org.apache.shiro.form-resubmit-port` system properties to restrict allowed connection targets.
Affected products
- Apache Shiro 2.x through 3.0.0
Timeline
- 2026-08-31: disclosed
- 2026-08-31: patched: Fixed in version 3.0.1