Vulnerabilities in pkg:maven/io.opentelemetry/opentelemetry-extension-trace-propagators
PACKAGECVE-2026-45292 is a MODERATE (CVSS 5.3) opentelemetry java sdk has unbounded vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Opentelemetry api libraries in the Maven ecosystem. The issue involves opentelemetry java sdk has unbounded memory allocation in w3c baggage propagation. Remediation is available by upgrading affected packages to version 1.62.0.
pkg:maven/io.opentelemetry/opentelemetry-extension-trace-propagators
Vulnerability advisories affecting package pkg:maven/io.opentelemetry/opentelemetry-extension-trace-propagators. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-rcgg-9c38-7xpx | CVE-2026-45292 | MODERATE | OpenTelemetry Java SDK has Unbounded Memory Allocation in W3C Baggage Propagation |
CVE-2026-45292 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
How to Fix CVE-2026-45292
To remediate this vulnerability, upgrade all affected Opentelemetry api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api</artifactId>
<version>1.62.0</version>
</dependency>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-extension-trace-propagators</artifactId>
<version>1.62.0</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.opentelemetry
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-45292, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.opentelemetry
Analyze the terminal output to locate any version of Opentelemetry api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.62.0), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.opentelemetry command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where 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. In Opentelemetry api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-45292 Affected Opentelemetry api Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.opentelemetry:opentelemetry-api
|
Maven |
< 1.62.0
|
1.62.0
|
|
io.opentelemetry:opentelemetry-extension-trace-propagators
|
Maven |
< 1.62.0
|
1.62.0
|
References
Frequently Asked Questions
What is CVE-2026-45292?
Which Opentelemetry api versions are affected?
What version fixes CVE-2026-45292?
Is opentelemetry-api affected?
Is opentelemetry-extension-trace-propagators affected?
What is the CVSS score of CVE-2026-45292?
What CWE is associated with CVE-2026-45292?
How can I check Maven dependencies for CVE-2026-45292?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rcgg-9c38-7xpx",
"modified" : "2026-06-09T02:01:11Z",
"published" : "2026-05-14T16:36:04Z",
"aliases" : [ "CVE-2026-45292" ],
"summary" : "OpenTelemetry Java SDK has Unbounded Memory Allocation in W3C Baggage Propagation",
"details" : "## Overview\n\nA vulnerability affects the baggage propagation implementation in\n`opentelemetry-api` and `opentelemetry-extension-trace-propagators`. Parsing oversized baggage\ncauses unbounded memory allocation and CPU consumption. Because baggage is automatically\nre-injected into every outgoing request, the effect can fan out to downstream services that\nnever received the original malicious request.\n\n## Technical Details\n\n- `W3CBaggagePropagator` did not enforce any limit on the total size or entry count of the\n `baggage` header. The parser iterated character-by-character through the entire value\n regardless of length.\n- `JaegerPropagator` and `OtTracePropagator` had the same gap in their respective baggage\n extraction paths.\n- The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of\n these limits were enforced.\n\n## Impact\n\nThe practical availability impact for most deployments is limited. Every major Java HTTP server\nenforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to\n8 KiB), constraining what an external attacker can deliver before the application is reached.\nThe risk is higher when transport-layer limits are absent — e.g., a compromised internal service\ncommunicating over a non-HTTP or custom transport.\n\n## Remediation\n\nUpdate to version 1.62.0 or later ([#8380](https://github.com/open-telemetry/opentelemetry-java/pull/8380)).\nThe fix enforces limits consistent with the W3C Baggage specification at the propagator level:\n\n- Maximum total baggage size: 8,192 bytes across all `baggage` header values\n- Maximum number of entries: 64\n\nHeaders that would exceed either limit are dropped at the point the limit is reached;\nalready-extracted valid entries are retained.\n\n## Workarounds\n\nEnsure HTTP header size limits are configured at the server or gateway level. Most Java HTTP\nservers enforce an 8 KiB header limit by default, which mitigates external attack vectors\nindependently of this fix.\n\n## References\n\n- [W3C Baggage Specification §Limits](https://www.w3.org/TR/baggage/#limits)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.opentelemetry:opentelemetry-api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.62.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.61.0"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "io.opentelemetry:opentelemetry-extension-trace-propagators"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.62.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.61.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-java/security/advisories/GHSA-rcgg-9c38-7xpx"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45292"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-java/pull/8380"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-java/commit/03837d3c1763bc35464aea1078671e2ef2336a5f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/open-telemetry/opentelemetry-java"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.62.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-14T16:36:04Z",
"nvd_published_at" : "2026-05-28T17:16:32Z"
}
}