Answer in brief
CVE-2026-50272 records a High severity (CVSS 7.5) vulnerability in dd-trace-js: Improper parsing of W3C baggage headers may lead to DoS. The current sources do not mark it as known exploited. The current feed maps dd-trace (npm), dd-trace (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dd-trace (npm), dd-trace (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dd-tracenpm | <5.100.0 | 5.100.0 |
| dd-tracenpm | >=0 <5.100.0 | 5.100.0 |
Published upstream
Jul 15, 2026
Evidence: source:nvd:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:nvd:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
### Impact Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing item-count or byte-size limits on the extract path. The DD_TRACE_BAGGAGE_MAX_ITEMS (default 64) and DD_TRACE_BAGGAGE_MAX_BYTES (default 8192) limits were applied only to baggage injection, not extraction. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs (or a single very large value). The tracer allocates a hash-map entry for each pair on every request, causing unbounded CPU and memory consumption and enabling a remote Denial of Service against any HTTP service that has the baggage propagation style enabled. The baggage propagation style is enabled by default in most affected tracers, so any internet-facing service that has been instrumented with an affected tracer version is exposed unless the propagation style has been explicitly narrowed. ### Patches This is resolved in version 5.100.0 and later of the `dd-trace-js` library. ### Workarounds If users cannot upgrade immediately: 1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATION_STYLE` (or `DD_TRACE_PROPAGATION_STYLE_EXTRACT` if set independently). 2. Cap the maximum HTTP request header size at an upstream proxy or web server (for example, Apache `LimitRequestFieldSize`, Nginx `large_client_header_buffers`, Envoy `max_request_headers_kb`). ### Resources Related upstream advisories: [opentelemetry-go GHSA-mh2q-q3fh-2475](https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475) [opentelemetry-dotnet GHSA-g94r-2vxg-569j](https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-g94r-2vxg-569j)
Quoted source text, attributed separately from HOL analysis.