Skip to content
Applications

CVE-2026-47858

8.0
High
EPSS 0.21%Patch availableJul 30, 2026

JMX-based RCE in Spring Tools when live information mode is enabled

common questions

Is CVE-2026-47858 being exploited?

Not confirmed. CVE-2026-47858 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-47858?

CVE-2026-47858 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47858?

Yes. A fix has been recorded for CVE-2026-47858. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-47858 affect?

CVE-2026-47858 affects Spring Tools for Eclipse <= 5.2.0, Spring Tools for VSCode / Cursor / Theia <= 2.2.0, Spring Boot apps started with live information mode enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47858?

Disable live information mode and avoid running untrusted apps; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Spring Tools for Eclipse <= 5.2.0Spring Tools for VSCode / Cursor / Theia <= 2.2.0Spring Boot apps started with live information mode enabled
impact

Remote code execution via exposed JMX when launching Spring Boot apps with live info enabled; attacker can execute arbitrary code as the user or container.

action required

Immediate action required

affected versions
Spring Spring Tools for Eclipse
  • affected<= 5.2.0
Spring Spring Tools for VSCode / Cursor / Theia
  • affected<= 2.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free