{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-59314 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-59314 is a low-severity vulnerability in Vmware Spring Framework, 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-59314 and fix it if it is affected.\n\nWhat it is: CVE-2026-59314 is a low-severity vulnerability in Vmware Spring Framework, 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-59314 in the wild and no public exploit code.\n\nAffected product: Vmware Spring Framework. 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-59314/ (Markdown: https://insights.sbomify.com/CVE-2026-59314/index.md)","id":"CVE-2026-59314","markdown":"https://insights.sbomify.com/CVE-2026-59314/index.md","name":"CVE-2026-59314","record":{"aliases":["CLEANSTART-2026-DS55761","CLEANSTART-2026-NX24657","CLEANSTART-2026-VD50036","DEBIAN-CVE-2026-59314","GHSA-j392-mc64-q79h","UBUNTU-CVE-2026-59314"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"none","summary":"Attackers can perform HTTP response splitting via malicious file names in Content-Disposition headers, affecting applications using Spring Framework.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_framework","vendor":"vmware"}],"cvss":{"score":3.7,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"Applications that build a Content-Disposition header value from untrusted input may be vulnerable to HTTP response splitting when the input is a malicious file name.\nSpring Framework 7.0.0 - 7.0.8\nSpring Framework 6.2.0 - 6.2.19\nSpring Framework 6.1.0 - 6.1.28\nSpring Framework 6.0.0 - 6.0.30\nSpring Framework 5.3.0 - 5.3.49\nSpring Framework 5.2.25.RELEASE and earlier","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 Framework response splitting in ContentDisposition","id":"CVE-2026-59314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:spring_framework","products":["vmware:spring_framework"],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring Cloud Config Monitor Denial of Service","id":"CVE-2026-59315"},"packages":[],"prev":{"headline":"Server Sent Event stream corruption in Spring MVC functional web framework","id":"CVE-2026-59313"},"products":["Spring Framework"],"published":"2026-08-27","related":[{"cvss_score":9.8,"headline":"Spring Framework Improper Path Limitation in XsltView","id":"CVE-2026-47884","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework Server Sent Event stream corruption while rendering fragments","id":"CVE-2026-47890","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder","id":"CVE-2026-47891","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints","id":"CVE-2026-47892","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Server Sent Event stream corruption in Spring MVC functional web framework","id":"CVE-2026-59313","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Pivotal Spring Framework contains unsafe Java deserialization methods","id":"CVE-2016-1000027","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":9.1,"headline":"Spring Framework Safety Guard Bypass via SpEL Expression Compilation","id":"CVE-2026-59283","kev_date_added":null,"published":"2026-08-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-09-01","vendors":["Spring"]},"summary":"Attackers can perform HTTP response splitting via malicious file names in Content-Disposition headers, affecting applications using Spring Framework.","url":"https://insights.sbomify.com/CVE-2026-59314/"}