{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.shiro:shiro-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23901 in the wild and no public exploit code.","fix":"Upgrade org.apache.shiro:shiro-core to 2.1.0 or later.","what":"CVE-2026-23901 is a low-severity vulnerability in Apache Shiro, published on 10 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-23901 and fix it if it is affected.\n\nWhat it is: CVE-2026-23901 is a low-severity vulnerability in Apache Shiro, published on 10 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-23901 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.shiro:shiro-core (Maven): affected all versions; fixed in 2.1.0\n- org.apache.shiro:shiro-core (Maven): affected all versions; fixed in 2.1.0\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-23901/ (Markdown: https://insights.sbomify.com/CVE-2026-23901/index.md)","id":"CVE-2026-23901","markdown":"https://insights.sbomify.com/CVE-2026-23901/index.md","name":"CVE-2026-23901","record":{"aliases":["CLEANSTART-2026-WY81634","CLEANSTART-2026-XU58754","DEBIAN-CVE-2026-23901","ECHO-d58c-d10e-42b1","GHSA-c4qc-4q9p-m9q9","MINI-2xmq-qc58-x2hx","MINI-42fc-w88x-wc5p","MINI-593v-p9qc-8hf9","MINI-5prg-86fp-vw6w","MINI-966v-wrrc-438g","MINI-c77g-fxcw-x25q","MINI-cpfr-cm94-r87v","MINI-g9x4-5mx4-5rr9","MINI-gg5p-ffh8-h37h","MINI-hhqv-mx6h-pmx8","MINI-hw8j-88g7-x6qr","MINI-jrjg-p9wv-mh8g","MINI-mxgc-c6xc-2669","MINI-pqp2-239g-37jv","MINI-qp29-8qw4-jp76","MINI-rf84-vc2x-fjwr","MINI-w9fc-xhgx-ppx6","MINI-xm2p-xphr-q4fw","MINI-xwp9-c2rf-58jv","UBUNTU-CVE-2026-23901"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java security library","requires_auth":"low_privilege","summary":"Attackers can enumerate valid usernames via timing discrepancies in Apache Shiro, facilitating targeted brute-force attacks.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"shiro","vendor":"apache"}],"cvss":{"score":1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/R:A/V:C/RE:L/U:Green","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Observable Timing Discrepancy vulnerability in Apache Shiro.\n\nThis issue affects Apache Shiro: from 1.*, 2.* before 2.0.7.\n\nUsers are recommended to upgrade to version 2.0.7 or later, which fixes the issue.\n\nPrior to Shiro 2.0.7, code paths for non-existent vs. existing users are different enough,\nthat a brute-force attack may be able to tell, by timing the requests only, determine if\nthe request failed because of a non-existent user vs. wrong password.\n\nThe most likely attack vector is a local attack only.\nShiro security model  https://shiro.apache.org/security-model.html#username_enumeration  discusses this as well.\n\nTypically, brute force attack can be mitigated at the infrastructure level.","ecosystems":["Maven"],"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: Brute force attack possible to determine valid user names","id":"CVE-2026-23901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Apache DolphinScheduler: Users are able to use tenants that are not defined on the platform during workflow execution.","id":"CVE-2026-23902"},"packages":[{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shiro:shiro-core","purl":null,"source":"GHSA-c4qc-4q9p-m9q9"},{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shiro:shiro-core","purl":"pkg:maven/org.apache.shiro/shiro-core","source":"GHSA-c4qc-4q9p-m9q9"}],"prev":{"headline":"Extension - phoca.cz - Stored XSS vectors in Phoca Maps component 5.0.0 - 6.0.2 for Joomla","id":"CVE-2026-23900"},"products":["Apache Shiro"],"published":"2026-02-10","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-02-10","vendors":["Apache Software Foundation"]},"summary":"Attackers can enumerate valid usernames via timing discrepancies in Apache Shiro, facilitating targeted brute-force attacks.","url":"https://insights.sbomify.com/CVE-2026-23901/"}