CVE-2026-45292 - Medium Severity Vulnerability
Vulnerable Library - opentelemetry-api-1.41.0.jar
OpenTelemetry API
Library home page: https://github.com/open-telemetry/opentelemetry-java
Path to dependency file: /OPENAPI-REST-API/openapi-client/kotlin/build.gradle
Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/io.opentelemetry/opentelemetry-api/1.41.0/ec5ad3b420c9fba4b340e85a3199fd0f2accd023/opentelemetry-api-1.41.0.jar
Dependency Hierarchy:
- swift-export-embeddable-2.2.20.jar (Root Library)
- ❌ opentelemetry-api-1.41.0.jar (Vulnerable Library)
Found in HEAD commit: 1f70e2feccb7006c8d32cc7d4fe62f5cf5e5c34d
Found in base branch: master
Vulnerability Details
Overview 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. Technical Details - "W3CBaggagePropagator" did not enforce any limit on the total size or entry count of the "baggage" header. The parser iterated character-by-character through the entire value regardless of length. - "JaegerPropagator" and "OtTracePropagator" had the same gap in their respective baggage extraction paths. - The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of these limits were enforced. Impact The practical availability impact for most deployments is limited. Every major Java HTTP server enforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to 8 KiB), constraining what an external attacker can deliver before the application is reached. The risk is higher when transport-layer limits are absent — e.g., a compromised internal service communicating over a non-HTTP or custom transport. Remediation Update to version 1.62.0 or later ("#8380" (open-telemetry/opentelemetry-java#8380)). The fix enforces limits consistent with the W3C Baggage specification at the propagator level: - Maximum total baggage size: 8,192 bytes across all "baggage" header values - Maximum number of entries: 64 Headers that would exceed either limit are dropped at the point the limit is reached; already-extracted valid entries are retained. Workarounds Ensure HTTP header size limits are configured at the server or gateway level. Most Java HTTP servers enforce an 8 KiB header limit by default, which mitigates external attack vectors independently of this fix. References - "W3C Baggage Specification §Limits" (https://www.w3.org/TR/baggage/#limits)
Publish Date: 2026-05-15
URL: CVE-2026-45292
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Step up your Open Source Security Game with Mend here
CVE-2026-45292 - Medium Severity Vulnerability
OpenTelemetry API
Library home page: https://github.com/open-telemetry/opentelemetry-java
Path to dependency file: /OPENAPI-REST-API/openapi-client/kotlin/build.gradle
Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/io.opentelemetry/opentelemetry-api/1.41.0/ec5ad3b420c9fba4b340e85a3199fd0f2accd023/opentelemetry-api-1.41.0.jar
Dependency Hierarchy:
Found in HEAD commit: 1f70e2feccb7006c8d32cc7d4fe62f5cf5e5c34d
Found in base branch: master
Overview 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. Technical Details - "W3CBaggagePropagator" did not enforce any limit on the total size or entry count of the "baggage" header. The parser iterated character-by-character through the entire value regardless of length. - "JaegerPropagator" and "OtTracePropagator" had the same gap in their respective baggage extraction paths. - The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of these limits were enforced. Impact The practical availability impact for most deployments is limited. Every major Java HTTP server enforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to 8 KiB), constraining what an external attacker can deliver before the application is reached. The risk is higher when transport-layer limits are absent — e.g., a compromised internal service communicating over a non-HTTP or custom transport. Remediation Update to version 1.62.0 or later ("#8380" (open-telemetry/opentelemetry-java#8380)). The fix enforces limits consistent with the W3C Baggage specification at the propagator level: - Maximum total baggage size: 8,192 bytes across all "baggage" header values - Maximum number of entries: 64 Headers that would exceed either limit are dropped at the point the limit is reached; already-extracted valid entries are retained. Workarounds Ensure HTTP header size limits are configured at the server or gateway level. Most Java HTTP servers enforce an 8 KiB header limit by default, which mitigates external attack vectors independently of this fix. References - "W3C Baggage Specification §Limits" (https://www.w3.org/TR/baggage/#limits)
Publish Date: 2026-05-15
URL: CVE-2026-45292
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.Step up your Open Source Security Game with Mend here