CVE-2026-33701

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenTelemetry Java Instrumentation provides OpenTelemetry auto-instrumentation and instrumentation libraries for Java. In versions prior to 2.26.1, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, an attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability: First, OpenTelemetry Java instrumentation is attached as a Java agent (-javaagent) on Java 16 or earlier. Second, JMX/RMI port has been explicitly configured via -Dcom.sun.management.jmxremote.port and is network-reachable. Third, gadget-chain-compatible library is present on the classpath. This results in arbitrary remote code execution with the privileges of the user running the instrumented JVM. For JDK >= 17, no action is required, but upgrading is strongly encouraged. For JDK < 17, upgrade to version 2.26.1 or later. As a workaround, set the system property -Dotel.instrumentation.rmi.enabled=false to disable the RMI integration.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 27, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Oct 13, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

Version 2.26.1

Patch available: open-telemetry/opentelemetry-java-instrumentation v2.26.1

https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.26.1
GitHub commit

commit 9cf4fbaaa9e7 (open-telemetry/opentelemetry-java-instrumentation)

Fix landed in open-telemetry/opentelemetry-java-instrumentation commit 9cf4fbaaa9e7 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/9cf4fbaaa9e79226142b2ed42a6f6b4ac0be2197
GitHub advisoryMentions a patch (unverified)

Unsafe deserialization in RMI instrumentation may lead to remote code execution · Advisory · open-telemetry/opentelemetry-java-instrumentation · GitHub

https://github.com/open-telemetry/opentelemetry-java-instrumentation/security/advisories/GHSA-xw7x-h9fj-p2c7
Red Hat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33701.json
Red Hat

2452071 – (CVE-2026-33701) CVE-2026-33701 io.opentelemetry.javaagent/opentelemetry-javaagent: OpenTelemetry Java Instrumentation: Remote code execution via deserialization vulnerability in RMI

https://bugzilla.redhat.com/show_bug.cgi?id=2452071
Red HatMentions a patch (unverified)

CVE-2026-33701 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-33701

Vendor Advisories for CVE-2026-33701(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.opentelemetry.javaagent:opentelemetry-javaagent0.12.0 ... 2.9.0 (106 versions)
  • every version up to 2.26.1: fixed in 2.26.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-14 09:19 UTCEG score recompute
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-13 06:38 UTCEG score recompute
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  6. 2026-10-12 16:13 UTCEG score recompute
  7. 2026-10-11 19:55 UTCEG score recompute
  8. 2026-10-11 17:08 UTCEG score recompute
  9. 2026-10-11 14:35 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  24. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  25. 2026-09-23 04:02 UTCOSV refresh
Show 68 more
  1. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  15. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-09-03 22:46 UTCOSV refresh
  17. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  18. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  24. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  27. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  28. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  29. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  30. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  31. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  33. 2026-08-17 12:13 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  35. 2026-08-16 10:03 UTCEG score recompute
  36. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  37. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  38. 2026-08-14 06:21 UTCEG score recompute
  39. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  40. 2026-08-12 20:39 UTCEG score recompute
  41. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  42. 2026-08-11 20:47 UTCEG score recompute
  43. 2026-08-11 03:49 UTCEG score recompute
  44. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  45. 2026-08-09 16:55 UTCEG score recompute
  46. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  47. 2026-08-09 05:54 UTCEG score recompute
  48. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  49. 2026-08-07 20:10 UTCEG score recompute
  50. 2026-08-06 18:44 UTCEG score recompute
  51. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  52. 2026-08-06 00:49 UTCEG score recompute
  53. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  54. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  55. 2026-08-04 12:35 UTCEG score recompute
  56. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  57. 2026-08-03 23:12 UTCEG score recompute
  58. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  59. 2026-08-02 15:14 UTCEG score recompute
  60. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  61. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  62. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  63. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  64. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  65. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  66. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  67. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  68. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile

Related CVEs(same product + same CWE)

Same product

2 shown

Maven:io.opentelemetry.javaagent:opentelemetry-javaagent

Frequently asked(5)

What is CVE-2026-33701?
CVE-2026-33701 is a critical-severity vulnerability; its CVE record was published on March 27, 2026. OpenTelemetry Java Instrumentation provides OpenTelemetry auto-instrumentation and instrumentation libraries for Java. In versions prior to 2.26.1, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and…
When was the CVE record for CVE-2026-33701 published?
The CVE record for CVE-2026-33701 was published on March 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-33701 actively exploited?
CVE-2026-33701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33701?
CVE-2026-33701 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-33701?
A fix for CVE-2026-33701 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33701 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33701

Explore →

Is Your Infrastructure Affected by CVE-2026-33701?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs