CVE-2026-54285: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-js
opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.
AI Analysis
Technical Summary
The OpenTelemetry JavaScript client (opentelemetry-js) versions before 2.8.0 contain a resource allocation vulnerability (CWE-770) in the W3CBaggagePropagator.extract() method within @opentelemetry/core. While the W3C Baggage specification recommends limiting baggage headers to 8,192 bytes and 180 entries, these limits were only enforced on outbound injection, not on inbound extraction. As a result, parsing oversized inbound baggage headers can cause memory allocation proportional to the header size without any limit, potentially leading to resource exhaustion. This vulnerability is addressed in version 2.8.0.
Potential Impact
This vulnerability can cause excessive memory allocation on systems processing oversized inbound baggage HTTP headers, potentially leading to denial of service due to resource exhaustion. There is no impact on confidentiality or integrity reported. The CVSS score is 5.3 (medium severity), reflecting the availability impact without requiring privileges or user interaction.
Mitigation Recommendations
Upgrade opentelemetry-js to version 2.8.0 or later, where the issue is fixed by enforcing size limits on inbound baggage headers. Patch status is confirmed fixed in 2.8.0. No other mitigations are indicated.
CVE-2026-54285: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-js
Description
opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OpenTelemetry JavaScript client (opentelemetry-js) versions before 2.8.0 contain a resource allocation vulnerability (CWE-770) in the W3CBaggagePropagator.extract() method within @opentelemetry/core. While the W3C Baggage specification recommends limiting baggage headers to 8,192 bytes and 180 entries, these limits were only enforced on outbound injection, not on inbound extraction. As a result, parsing oversized inbound baggage headers can cause memory allocation proportional to the header size without any limit, potentially leading to resource exhaustion. This vulnerability is addressed in version 2.8.0.
Potential Impact
This vulnerability can cause excessive memory allocation on systems processing oversized inbound baggage HTTP headers, potentially leading to denial of service due to resource exhaustion. There is no impact on confidentiality or integrity reported. The CVSS score is 5.3 (medium severity), reflecting the availability impact without requiring privileges or user interaction.
Mitigation Recommendations
Upgrade opentelemetry-js to version 2.8.0 or later, where the issue is fixed by enforcing size limits on inbound baggage headers. Patch status is confirmed fixed in 2.8.0. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-12T17:46:37.292Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a39735ceed863c81e3962a1
Added to database: 06/22/2026, 17:39:40 UTC
Last enriched: 06/29/2026, 21:51:53 UTC
Last updated: 08/05/2026, 12:41:16 UTC
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.