{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41707 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-41707 is a high-severity authentication bypass vulnerability in Spring Security, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41707 and fix it if it is affected.\n\nWhat it is: CVE-2026-41707 is a high-severity authentication bypass vulnerability in Spring Security, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41707 in the wild and no public exploit code.\n\nAffected product: Spring Security. 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-41707/ (Markdown: https://insights.sbomify.com/CVE-2026-41707/index.md)","id":"CVE-2026-41707","markdown":"https://insights.sbomify.com/CVE-2026-41707/index.md","name":"CVE-2026-41707","record":{"aliases":["CLEANSTART-2026-CJ91094","CLEANSTART-2026-LZ14873","ECHO-5b8b-ed94-89df","GHSA-3488-4mh8-47j4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can bypass authentication by evicting cache entries and replaying intercepted DPoP proofs in Spring Security.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_security","vendor":"vmware"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Authentication Bypass by Capture-replay vulnerability in Spring Spring Security allows Spring Security's DPoPProofJwtDecoderFactory contains a cache-based replay attack vulnerability. The internal cache storing JWT ID claims has a strict size limit, allowing attackers to evict legitimate entries by flooding the server with dummy requests, then replay intercepted valid DPoP proofs.\n\nThis issue affects Spring Security: 7.1.0, from 7.0.0 through 7.0.6, and from 6.5.0 through 6.5.11.","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":"Spring Security DPoPProofJwtDecoderFactory vulnerable to DPoP Proof Replay","id":"CVE-2026-41707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring Cloud Sleuth instrumentation of Spring TX DoS vulnerability","id":"CVE-2026-41708"},"packages":[],"prev":{"headline":"Open Redirect When Using CookieRequestCache","id":"CVE-2026-41706"},"products":["Spring Security"],"published":"2026-08-25","related":[{"cvss_score":9.8,"headline":"Authorization Bypass in Spring Security","id":"CVE-2014-3527","kev_date_added":null,"published":"2017-05-25"},{"cvss_score":9.6,"headline":"Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata","id":"CVE-2026-59354","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.4,"headline":"Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces","id":"CVE-2026-59270","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.1,"headline":"Under Some Conditions Spring Security HTTP Headers Are not Written","id":"CVE-2026-22732","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":9.1,"headline":"Access Control Bypass in Spring Security","id":"CVE-2023-34034","kev_date_added":null,"published":"2023-07-19"},{"cvss_score":8.2,"headline":"Spring Security Authorization Server Default Consent Page is vulnerable to Cross-Site Scripting (XSS)","id":"CVE-2026-47877","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":8.1,"headline":"Deserialization of Untrusted Data in Spring Security","id":"CVE-2017-4995","kev_date_added":null,"published":"2017-11-27"}],"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":"total"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["Spring"]},"summary":"Attackers can bypass authentication by evicting cache entries and replaying intercepted DPoP proofs in Spring Security.","url":"https://insights.sbomify.com/CVE-2026-41707/"}