{"answers":{"affected":"2 open source packages ship an affected version, including org.springframework.cloud:spring-cloud-sleuth-instrumentation. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41708 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41708 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41708 is a high-severity denial of service vulnerability in Spring Cloud Sleuth, published on 15 Jun 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-41708 and fix it if it is affected.\n\nWhat it is: CVE-2026-41708 is a high-severity denial of service vulnerability in Spring Cloud Sleuth, published on 15 Jun 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-41708 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.cloud:spring-cloud-sleuth-instrumentation (Maven): affected from 3.1.0 up to 3.1.11; no fix listed\n- org.springframework.cloud:spring-cloud-sleuth-instrumentation (Maven): affected from 3.1.0 up to 3.1.11; no fix listed\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-41708/ (Markdown: https://insights.sbomify.com/CVE-2026-41708/index.md)","id":"CVE-2026-41708","markdown":"https://insights.sbomify.com/CVE-2026-41708/index.md","name":"CVE-2026-41708","record":{"aliases":["GHSA-26m2-9g2q-v45q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Cloud Sleuth","requires_auth":"none","summary":"Crafted calls cause denial of service in Spring Cloud Sleuth when Spring TX instrumentation is enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_cloud_sleuth","vendor":"broadcom"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"In Spring Cloud Sleuth, it is possible for a user to provide specially crafted calls that may cause a denial-of-service (DoS) condition. The application is vulnerable when it uses a vulnerable version of org.springframework.cloud:spring-cloud-sleuth-instrumentation and Spring TX instrumentation is not disabled.\n\nAffected versions:\nSpring Cloud Sleuth 3.1.0 through 3.1.13.","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":false,"headline":"Spring Cloud Sleuth instrumentation of Spring TX DoS vulnerability","id":"CVE-2026-41708","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Broadcom VMWare ESX Insufficient Logging","id":"CVE-2026-41709"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["3.1.0"],"last_affected":["3.1.11"],"package":"org.springframework.cloud:spring-cloud-sleuth-instrumentation","purl":null,"source":"GHSA-26m2-9g2q-v45q"},{"ecosystem":"Maven","fixed":[],"introduced":["3.1.0"],"last_affected":["3.1.11"],"package":"org.springframework.cloud:spring-cloud-sleuth-instrumentation","purl":"pkg:maven/org.springframework.cloud/spring-cloud-sleuth-instrumentation","source":"GHSA-26m2-9g2q-v45q"}],"prev":{"headline":"Spring Security DPoPProofJwtDecoderFactory vulnerable to DPoP Proof Replay","id":"CVE-2026-41707"},"products":["Spring Cloud Sleuth"],"published":"2026-06-15","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-15","vendors":["Spring"]},"summary":"Crafted calls cause denial of service in Spring Cloud Sleuth when Spring TX instrumentation is enabled.","url":"https://insights.sbomify.com/CVE-2026-41708/"}