{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-47893 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-47893 is a high-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-47893 and fix it if it is affected.\n\nWhat it is: CVE-2026-47893 is a high-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-47893 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-47893/ (Markdown: https://insights.sbomify.com/CVE-2026-47893/index.md)","id":"CVE-2026-47893","markdown":"https://insights.sbomify.com/CVE-2026-47893/index.md","name":"CVE-2026-47893","record":{"aliases":["CLEANSTART-2026-AY49632","CLEANSTART-2026-CU45491","CLEANSTART-2026-IY13000","CLEANSTART-2026-TS74004","DEBIAN-CVE-2026-47893","GHSA-vw3r-pj6g-mjg8","UBUNTU-CVE-2026-47893"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Framework","requires_auth":"none","summary":"Attackers can view sensitive request headers via exception messages in Spring WebFlux WebSocket applications, potentially exposing user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_framework","vendor":"vmware"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"A Spring WebFlux application that supports WebSocket connections may expose indirectly sensitive user information by including request headers in an exception reason.\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 Request Headers Included in Exception Reasons in HandshakeWebsocketService","id":"CVE-2026-47893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:spring_framework","products":["vmware:spring_framework"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring Cloud Config Server Native Environment Repository Exposure","id":"CVE-2026-47894"},"packages":[],"prev":{"headline":"Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints","id":"CVE-2026-47892"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Spring"]},"summary":"Attackers can view sensitive request headers via exception messages in Spring WebFlux WebSocket applications, potentially exposing user data.","url":"https://insights.sbomify.com/CVE-2026-47893/"}