Loading vulnerability…
CVE-2026-47858 is a remote code execution vulnerability in Spring Tools that affects Spring Tools for Eclipse 5.2.0 and earlier and Spring Tools for VSCode, Cursor, and Theia 2.2.0 and earlier. When a Spring Boot application is started from affected Spring Tools with live information mode enabled, the running application becomes exposed to JMX-based remote code execution. The issue arises from the way live information startup mode configures or exposes JMX functionality, allowing an attacker to reach a management interface that should not be remotely exploitable. The vulnerability affects the launched application context rather than only the IDE itself, and successful exploitation can result in arbitrary code execution within the security context of the targeted Spring Boot application process.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a working proof-of-concept/operational exploit for CVE-2026-47858, targeting Spring Tools live-information mode JMX exposure. The repo contains: (1) attack orchestration in bash (attack.sh), (2) a Java exploit client (attacker/JmxExploit.java) that connects to the target RMI registry, looks up the jmxrmi binding, rewrites the advertised RMI stub host from localhost to the real target IP via reflection, authenticates with RMIServer.newClient(null) using no credentials, and invokes the MLet service to load attacker-controlled code; (3) a malicious Java payload (exploit-server/evil/Pwn.java) implementing DynamicMBean whose constructor executes arbitrary shell commands via /bin/sh -c and writes proof/output files under /tmp; and (4) a lab environment (run-lab.sh plus victim-app/) that builds and launches a demo Spring Boot app inside Docker under vulnerable and fixed JVM argument sets. Main exploit capability: unauthenticated adjacent-network RCE against vulnerable IDE-launched Spring Boot apps. The exploit is not merely detection; it performs end-to-end compromise by serving mlet.txt and evil.jar over HTTP, then causing the victim JVM to fetch and instantiate the payload class. Commands are operator-controlled at runtime through the generated MLet <ARG> value, so the payload JAR is command-agnostic and reusable without recompilation. The included NaiveJmxClient.java demonstrates that a default client fails because the vulnerable configuration advertises localhost in the RMI stub; JmxExploit.java bypasses this by reflective host rewriting. Repository structure is clean and purpose-built: README files document the vulnerability and usage; attack.sh automates payload build, MLet generation, HTTP serving, exploit execution, and optional Docker verification; exploit-server/ contains the malicious class and MLet template; attacker/ contains the exploit and a control client; victim-app/ is a minimal Spring Boot 4.0.7 web/actuator application used for reproduction. Overall, this is a real exploit repository with configurable command execution and a reproducible lab, not a framework module or a simple scanner.
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 remote code execution vulnerability in Spring Tools related to live information startup mode.
A remote code execution vulnerability in Spring live information startup mode.
A JMX-based remote code execution vulnerability affecting Spring Tools when Spring Boot applications are started with live information mode enabled.
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.