Skip to content

OpenTelemetry Javaagent RMI context propagation allows resource exhaustion

Moderate severity GitHub Reviewed Published Jun 9, 2026 in open-telemetry/opentelemetry-java-instrumentation • Updated Jul 29, 2026

Package

maven io.opentelemetry.javaagent:opentelemetry-javaagent (Maven)

Affected versions

< 2.27.0

Patched versions

2.27.0

Description

The RMI context propagation payload reader limits the number of context entries but does not limit the aggregate size of the strings read from the stream.

An attacker who can reach an RMI endpoint on an instrumented JVM can send an oversized context propagation payload. This can cause excessive memory allocation while the JVM reads the payload, potentially leading to denial of service.

The issue affects only deployments where RMI instrumentation is enabled and an RMI endpoint is network-reachable.

References

@trask trask published to open-telemetry/opentelemetry-java-instrumentation Jun 9, 2026
Published by the National Vulnerability Database Jul 1, 2026
Published to the GitHub Advisory Database Jul 29, 2026
Reviewed Jul 29, 2026
Last updated Jul 29, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(18th percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

CVE ID

CVE-2026-54712

GHSA ID

GHSA-fq3f-m5qm-99f5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.