{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-59276 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-59276 is a medium-severity vulnerability in Spring Security, published on 27 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-59276 and fix it if it is affected.\n\nWhat it is: CVE-2026-59276 is a medium-severity vulnerability in Spring Security, published on 27 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-59276 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-59276/ (Markdown: https://insights.sbomify.com/CVE-2026-59276/index.md)","id":"CVE-2026-59276","markdown":"https://insights.sbomify.com/CVE-2026-59276/index.md","name":"CVE-2026-59276","record":{"aliases":["CLEANSTART-2026-AA31447","CLEANSTART-2026-EV98830","CLEANSTART-2026-SI92815","ECHO-1d47-61cb-67e8","GHSA-vj7f-9q44-g5xv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can exploit timing differences in string comparisons to infer sensitive security values, potentially leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_security","vendor":"vmware"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Several components in Spring Security compare security-sensitive values using standard string equality (String.equals()) rather than a constant-time comparison. Because String.equals() returns as soon as it finds a differing character, the time taken to reject an incorrect value is proportional to the number of leading characters that match the expected value.\nSpring Security 7.1.0\nSpring Security 7.0.0 - 7.0.6\nSpring Security 6.5.0 - 6.5.11\nSpring Security 6.4.0 - 6.4.18\nSpring Security 5.8.0 - 5.8.27\nSpring Security 5.7.0 - 5.7.25","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":"Timing Attack via Non-Constant-Time Comparison of Sensitive Values","id":"CVE-2026-59276","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring Security InetAddressMatchers Incomplete Internal Network Classification","id":"CVE-2026-59277"},"packages":[],"prev":{"headline":"Deserialization in Spring AMQP","id":"CVE-2026-59275"},"products":["Spring Security"],"published":"2026-08-27","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":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Spring"]},"summary":"Attackers can exploit timing differences in string comparisons to infer sensitive security values, potentially leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2026-59276/"}