VulnerabilityPublished 28 May 2026Updated 17 Sep 2026

CVE-2026-45292: open-telemetry opentelemetry-java · Unthrottled Resource Allocation

Affects open-telemetry opentelemetry-javaSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.62.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.62.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade opentelemetry-java and io.opentelemetry/opentelemetry-api and io.opentelemetry/opentelemetry-extension-trace-propagators to 1.62.0.

Affected software

Product	Affected	Fixed in
open-telemetryopentelemetry-java	Affected <1.62.0	Fixed in 1.62.0
io.opentelemetryopentelemetry-api	Affected =1.62.0	Fixed in–
io.opentelemetryopentelemetry-extension-trace-propagators	Affected =1.62.0	Fixed in–
Mavenio.opentelemetry/opentelemetry-api`pkg:maven/io.opentelemetry/opentelemetry-api`Other threats	Affected <1.62.0	Fixed in 1.62.0
Mavenio.opentelemetry/opentelemetry-extension-trace-propagators`pkg:maven/io.opentelemetry/opentelemetry-extension-trace-propagators`Other threats	Affected <1.62.0	Fixed in 1.62.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official fix is available in opentelemetry-java version 1.62.0. Users should upgrade to version 1.62.0 or later to remediate this vulnerability. No additional mitigations are specified in the vendor advisory. Since this is not a cloud service, remediation is the responsibility of the user.

Description

opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.62.0, a vulnerability affects the baggage propagation implementation in opentelemetry-api and opentelemetry-extension-trace-propagators. Parsing oversized baggage causes unbounded memory allocation and CPU consumption. Because baggage is automatically re-injected into every outgoing request, the effect can fan out to downstream services that never received the original malicious request. This vulnerability is fixed in 1.62.0.

Impact

The vulnerability allows a remote attacker to cause unbounded memory allocation and high CPU consumption in affected services, resulting in denial of service. The automatic re-injection of baggage into outgoing requests means the impact can extend beyond the initially targeted service to downstream services, potentially amplifying the denial of service effect. There is no impact on confidentiality or integrity, only availability is affected.

Summary

CVE-2026-45292 affects the Java implementation of OpenTelemetry's API and SDK, specifically the baggage propagation feature. When processing oversized baggage, the affected versions allocate memory and consume CPU resources without limits, leading to a denial of service condition. The vulnerability can be exploited remotely by sending maliciously large baggage data, and due to automatic re-injection of baggage into outgoing requests, the denial of service effect can cascade to downstream services. The issue is tracked under CWE-770 (Allocation of Resources Without Limits or Throttling) and has been addressed in opentelemetry-java version 1.62.0.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Aug 2026, 16:35 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats