{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-58301 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-58301 is a medium-severity server-side request forgery vulnerability in Apache Shiro, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-58301 and fix it if it is affected.\n\nWhat it is: CVE-2026-58301 is a medium-severity server-side request forgery vulnerability in Apache Shiro, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-58301 in the wild and no public exploit code.\n\nAffected product: Apache Shiro. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58301/ (Markdown: https://insights.sbomify.com/CVE-2026-58301/index.md)","id":"CVE-2026-58301","markdown":"https://insights.sbomify.com/CVE-2026-58301/index.md","name":"CVE-2026-58301","record":{"aliases":["CLEANSTART-2026-SB52604","DEBIAN-CVE-2026-58301","GHSA-r2fv-9rvj-c54c","UBUNTU-CVE-2026-58301"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Java security library","requires_auth":"low_privilege","summary":"A low-privileged user can force the server to connect to an attacker-controlled URL via the Jakarta EE integration module, enabling data exfiltration or modification.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"shiro","vendor":"apache"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/S:P/AU:Y/R:U/V:D/RE:L/U:Amber","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.\n\nMitigation: Upgrade to version 3.0.1 or later, which fixes the issue. +\nAlternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Shiro: Server-side POST request may be steered to an alternate host","id":"CVE-2026-58301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in LinuxCNC","id":"CVE-2026-58302"},"packages":[],"prev":{"headline":"Microsoft Edge for Android Information Disclosure Vulnerability","id":"CVE-2026-58300"},"products":["Apache Shiro"],"published":"2026-08-31","related":[{"cvss_score":9.8,"headline":"Path Traversal in Apache Shiro","id":"CVE-2023-34478","kev_date_added":null,"published":"2023-07-24"},{"cvss_score":9.8,"headline":"Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher","id":"CVE-2022-40664","kev_date_added":null,"published":"2022-10-12"},{"cvss_score":9.8,"headline":"Authentication Bypass Vulnerability","id":"CVE-2022-32532","kev_date_added":null,"published":"2022-06-28"},{"cvss_score":9.8,"headline":"Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass","id":"CVE-2021-41303","kev_date_added":null,"published":"2021-09-17"},{"cvss_score":9.8,"headline":"Authentication bypass in Apache Shiro","id":"CVE-2020-17523","kev_date_added":null,"published":"2021-02-03"},{"cvss_score":9.8,"headline":"Authentication bypass in Apache Shiro","id":"CVE-2020-17510","kev_date_added":null,"published":"2020-11-05"},{"cvss_score":9.8,"headline":"Improper Authentication in Apache Shiro","id":"CVE-2020-11989","kev_date_added":null,"published":"2020-06-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["Apache Software Foundation"]},"summary":"A low-privileged user can force the server to connect to an attacker-controlled URL via the Jakarta EE integration module, enabling data exfiltration or modification.","url":"https://insights.sbomify.com/CVE-2026-58301/"}