Loading vulnerability…
CVE-2026-47882 is a weakness in Spring Tools for Eclipse affecting version 5.2.0 and earlier. When the Spring Tools Boot Dashboard is used to enable Spring Boot DevTools support for a remote application target, such as a Docker container or Cloud Foundry application, the tooling generates the shared secret used to authenticate DevTools remote-restart uploads to the deployed application. That secret is generated with a non-cryptographic pseudo-random number generator rather than a cryptographically secure source of randomness. As a result, the entropy and unpredictability of the authentication secret may be insufficient for its security purpose, weakening the trust boundary around the remote-restart mechanism.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability where the Spring Boot DevTools remote secret is generated using a non-cryptographic pseudo-random number generator.
A vulnerability where the Spring Boot DevTools remote secret is generated using a non-cryptographic pseudo-random number generator.
A vulnerability in Spring Tools for Eclipse where a shared secret used for Spring Boot DevTools remote-restart authentication was generated with a non-cryptographic pseudo-random number generator instead of a cryptographically secure source of randomness.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.