{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-47882 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47882 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47882 is a high-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47882 and fix it if it is affected.\n\nWhat it is: CVE-2026-47882 is a high-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47882 in the wild and no public exploit code.\n\nAffected product: Spring Tools for Eclipse. 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-47882/ (Markdown: https://insights.sbomify.com/CVE-2026-47882/index.md)","id":"CVE-2026-47882","markdown":"https://insights.sbomify.com/CVE-2026-47882/index.md","name":"CVE-2026-47882","record":{"aliases":["GHSA-cpfc-g4p9-rg24"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Spring Tools for Eclipse","requires_auth":"none","summary":"Developers using Spring Tools for Eclipse to deploy remote DevTools may face authentication bypass due to weak secret generation.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_tools","vendor":"broadcom"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"When enabling Spring Boot DevTools support for a remote application target (for example a Docker container or Cloud Foundry app) from the Spring Tools Boot Dashboard, Spring Tools generates a shared secret that authenticates DevTools remote-restart uploads to the deployed application. This secret was generated using a non-cryptographic pseudo-random number generator rather than a cryptographically secure source of randomness.\nAffected Spring Products and Versions:\nSpring Tools for Eclipse: 5.2.0 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":false,"headline":"Spring Boot DevTools remote secret generated with a non-cryptographic PRNG","id":"CVE-2026-47882","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring Framework Open Redirect in UrlHandlerFilter","id":"CVE-2026-47883"},"packages":[],"prev":{"headline":"Denial of Service in Spring Batch FlatFileItemReader via Malformed Input File","id":"CVE-2026-47881"},"products":["Spring Tools for Eclipse"],"published":"2026-07-30","related":[{"cvss_score":8,"headline":"live information startup mode is vulnerable for remote code execution","id":"CVE-2026-47858","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":8,"headline":"Spring Tools Docker integration publishes unauthenticated debug (JDWP) and JMX ports on all network interfaces","id":"CVE-2026-47873","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":4.4,"headline":"Cleartext Storage of Spring Boot DevTools Remote Secret in Eclipse Launch Configurations","id":"CVE-2026-59327","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":4.2,"headline":"Cross-Site Scripting in Eclipse Spring Boot Starter Wizard Dependency Tooltips","id":"CVE-2026-59328","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":3.3,"headline":"HTTP Proxy Credentials Logged in Plaintext by the Spring Boot Language Server","id":"CVE-2026-59326","kev_date_added":null,"published":"2026-07-30"}],"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-01","vendors":["Spring"]},"summary":"Developers using Spring Tools for Eclipse to deploy remote DevTools may face authentication bypass due to weak secret generation.","url":"https://insights.sbomify.com/CVE-2026-47882/"}