CVE-2026-33701

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

March 27, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Aug 24, 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 Patch Available

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
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33701.json
redhat

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
redhat Patch Available

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 rangeFixed inDependents
io.opentelemetry.javaagent:opentelemetry-javaagent0.12.0 ... 2.9.0 (106 versions)2.26.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-28 21:41 UTCEPSS rescore
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 14:17 UTCEPSS rescore
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 12:13 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 10:03 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 06:21 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 20:39 UTCEG score recompute
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 20:47 UTCEG score recompute
  23. 2026-08-11 03:49 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 16:55 UTCEG score recompute
Show 59 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-09 05:54 UTCEG score recompute
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-07 20:10 UTCEG score recompute
  5. 2026-08-06 18:44 UTCEG score recompute
  6. 2026-08-06 13:46 UTCEPSS rescore
  7. 2026-08-06 00:49 UTCEG score recompute
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 15:10 UTCEPSS rescore
  10. 2026-08-04 12:35 UTCEG score recompute
  11. 2026-08-04 10:38 UTCEPSS rescore
  12. 2026-08-03 23:12 UTCEG score recompute
  13. 2026-08-03 10:36 UTCEPSS rescore
  14. 2026-08-02 15:14 UTCEG score recompute
  15. 2026-08-02 02:27 UTCEPSS rescore
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-27 14:13 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-25 14:18 UTCEPSS rescore
  23. 2026-07-25 14:18 UTCEPSS rescore
  24. 2026-07-24 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:09 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:24 UTCEPSS rescore
  31. 2026-07-20 17:08 UTCEPSS rescore
  32. 2026-07-19 14:31 UTCEPSS rescore
  33. 2026-07-19 02:29 UTCEPSS rescore
  34. 2026-07-18 10:04 UTCEPSS rescore
  35. 2026-07-18 06:59 UTCOSV refresh
  36. 2026-07-16 17:03 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  42. 2026-07-13 22:30 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-08 15:15 UTCEPSS rescore
  49. 2026-07-07 13:46 UTCEPSS rescore
  50. 2026-07-06 16:27 UTCEPSS rescore
  51. 2026-07-06 16:27 UTCEPSS rescore
  52. 2026-07-06 02:23 UTCEPSS rescore
  53. 2026-07-06 02:23 UTCEPSS rescore
  54. 2026-07-05 02:30 UTCEPSS rescore
  55. 2026-07-04 06:31 UTCEPSS rescore
  56. 2026-07-01 15:06 UTCEPSS rescore
  57. 2026-06-30 23:22 UTCEPSS rescore
  58. 2026-06-30 04:32 UTCEG score recompute
  59. 2026-06-30 04:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-33701?
CVE-2026-33701 is a critical vulnerability 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 CVE-2026-33701 disclosed?
CVE-2026-33701 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33701 actively exploited?
CVE-2026-33701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33701, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs