Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2026-33701

A vulnerability in OpenTelemetry Java Instrumentation allows for unsafe data processing during RMI (Remote Method Invocation) operations. If certain conditions are met, an attacker can send malicious data that the system processes insecurely, potentially leading to unauthorized command execution.

publishedMar 27, 2026
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
<1%
57th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Users running OpenTelemetry Java Instrumentation (versions prior to 2.26.1) on JDK 16 or earlier, where JMX/RMI ports are network-reachable and a compatible library is present on the classpath.

02

Real-world impact

An attacker with network access to a configured JMX or RMI port could execute arbitrary code on the server, running with the same permissions as the user running the Java application.

03

Why this severity

The critical score reflects that the vulnerability can be exploited remotely over a network without requiring user interaction or special privileges, potentially leading to full system compromise.

04

What to do about it

official fix available
recommended steps
  1. 01If using JDK 16 or earlier, upgrade OpenTelemetry Java Instrumentation to version 2.26.1 or later.
  2. 02If using JDK 17 or later, upgrade to version 2.26.1 or later as a best practice.
interim mitigations
  • Set the system property -Dotel.instrumentation.rmi.enabled=false to disable RMI integration.

NVD-referenced vendor advisory

05

Timeline

  1. Mar 27, 2026 · Mar 27, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 22h ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 20h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →