GHSA-wxqq-gcq8-c443: dd-trace-js: Improper parsing of W3C baggage headers may lead to DoS
The dd-trace-js library versions prior to 5.100.0 improperly parse W3C baggage HTTP headers during extraction without enforcing limits on item count or byte size. This allows a remote attacker to send a request with a very large or numerous baggage header entries, causing unbounded CPU and memory consumption and resulting in a denial of service. The baggage propagation style is enabled by default in most affected tracers, exposing internet-facing services instrumented with these versions unless explicitly restricted.
AI Analysis
Technical Summary
Datadog's dd-trace-js library versions before 5.100.0 have a vulnerability in the handling of W3C baggage headers. While limits on baggage size and item count are enforced during baggage injection, these limits were not applied during baggage extraction. An unauthenticated remote attacker can exploit this by sending HTTP requests with excessively large or numerous baggage header key-value pairs. Each pair causes the tracer to allocate hash-map entries, leading to unbounded CPU and memory usage and enabling a remote denial of service against services using the affected tracer with baggage propagation enabled. The vulnerability is resolved in version 5.100.0 and later.
Potential Impact
A remote, unauthenticated attacker can cause a denial of service by sending specially crafted HTTP requests with large or numerous baggage header entries. This leads to excessive CPU and memory consumption in the dd-trace-js library during baggage extraction, potentially disrupting the availability of any HTTP service instrumented with affected versions of the tracer that have baggage propagation enabled.
Mitigation Recommendations
A fix is available in dd-trace-js version 5.100.0 and later; upgrading to this version or newer is recommended. If immediate upgrade is not possible, users can mitigate by disabling baggage extraction via configuration (removing 'baggage' from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT). Additionally, capping the maximum HTTP request header size at an upstream proxy or web server (e.g., Apache LimitRequestFieldSize, Nginx large_client_header_buffers, Envoy max_request_headers_kb) can help prevent exploitation.
GHSA-wxqq-gcq8-c443: dd-trace-js: Improper parsing of W3C baggage headers may lead to DoS
Description
The dd-trace-js library versions prior to 5.100.0 improperly parse W3C baggage HTTP headers during extraction without enforcing limits on item count or byte size. This allows a remote attacker to send a request with a very large or numerous baggage header entries, causing unbounded CPU and memory consumption and resulting in a denial of service. The baggage propagation style is enabled by default in most affected tracers, exposing internet-facing services instrumented with these versions unless explicitly restricted.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Datadog's dd-trace-js library versions before 5.100.0 have a vulnerability in the handling of W3C baggage headers. While limits on baggage size and item count are enforced during baggage injection, these limits were not applied during baggage extraction. An unauthenticated remote attacker can exploit this by sending HTTP requests with excessively large or numerous baggage header key-value pairs. Each pair causes the tracer to allocate hash-map entries, leading to unbounded CPU and memory usage and enabling a remote denial of service against services using the affected tracer with baggage propagation enabled. The vulnerability is resolved in version 5.100.0 and later.
Potential Impact
A remote, unauthenticated attacker can cause a denial of service by sending specially crafted HTTP requests with large or numerous baggage header entries. This leads to excessive CPU and memory consumption in the dd-trace-js library during baggage extraction, potentially disrupting the availability of any HTTP service instrumented with affected versions of the tracer that have baggage propagation enabled.
Mitigation Recommendations
A fix is available in dd-trace-js version 5.100.0 and later; upgrading to this version or newer is recommended. If immediate upgrade is not possible, users can mitigate by disabling baggage extraction via configuration (removing 'baggage' from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT). Additionally, capping the maximum HTTP request header size at an upstream proxy or web server (e.g., Apache LimitRequestFieldSize, Nginx large_client_header_buffers, Envoy max_request_headers_kb) can help prevent exploitation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wxqq-gcq8-c443
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-50272"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a58b40468715ace43d6705c
Added to database: 07/16/2026, 10:35:48 UTC
Last enriched: 07/16/2026, 10:48:18 UTC
Last updated: 07/16/2026, 11:48:10 UTC
Views: 3
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.
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.