CVE-2026-54285: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-js
A vulnerability in opentelemetry-js prior to version 2.8.0 allows unbounded memory allocation when parsing inbound baggage HTTP headers due to lack of size limits enforcement in the extract() function of W3CBaggagePropagator. This can lead to resource exhaustion. The issue is fixed in version 2.8.0.
AI Analysis
Technical Summary
The OpenTelemetry JavaScript client (opentelemetry-js) versions before 2.8.0 contain a vulnerability (CWE-770) where the W3CBaggagePropagator.extract() method does not enforce the recommended size limits on inbound baggage HTTP headers. While the outbound inject() method enforces limits per the W3C Baggage specification (maximum 8,192 bytes and 180 entries), the extract() method allows parsing of oversized baggage headers without caps, causing memory allocation proportional to the header size. This can result in excessive resource consumption. The vulnerability is addressed in version 2.8.0.
Potential Impact
This vulnerability can cause a denial of service condition by exhausting memory resources when processing oversized inbound baggage headers. There is no impact on confidentiality or integrity. The CVSS score is 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact limited to availability (memory exhaustion).
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. No other mitigations are specified. Patch status is not explicitly stated but the fix is available in version 2.8.0.
CVE-2026-54285: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-js
Description
A vulnerability in opentelemetry-js prior to version 2.8.0 allows unbounded memory allocation when parsing inbound baggage HTTP headers due to lack of size limits enforcement in the extract() function of W3CBaggagePropagator. This can lead to resource exhaustion. The issue is fixed in version 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 vulnerability (CWE-770) where the W3CBaggagePropagator.extract() method does not enforce the recommended size limits on inbound baggage HTTP headers. While the outbound inject() method enforces limits per the W3C Baggage specification (maximum 8,192 bytes and 180 entries), the extract() method allows parsing of oversized baggage headers without caps, causing memory allocation proportional to the header size. This can result in excessive resource consumption. The vulnerability is addressed in version 2.8.0.
Potential Impact
This vulnerability can cause a denial of service condition by exhausting memory resources when processing oversized inbound baggage headers. There is no impact on confidentiality or integrity. The CVSS score is 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact limited to availability (memory exhaustion).
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. No other mitigations are specified. Patch status is not explicitly stated but the fix is available in version 2.8.0.
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/22/2026, 17:55:03 UTC
Last updated: 06/22/2026, 20:37:22 UTC
Views: 5
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.