{"id":"GHSA-p5f6-rccc-jv98","summary":"dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS","details":"### Impact\nDatadog 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.\nThe 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.\n\n### Patches\nThis is resolved in version 2.32.0 and later of the `dd-trace-rb` library.\n\n### Workarounds\nIf users cannot upgrade immediately:\n1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATION_STYLE` (or `DD_TRACE_PROPAGATION_STYLE_EXTRACT` if set independently).\n2. 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`).\n\n\n### Resources\nRelated upstream advisories:\n[opentelemetry-go GHSA-mh2q-q3fh-2475](https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475)\n[opentelemetry-dotnet GHSA-g94r-2vxg-569j](https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-g94r-2vxg-569j)","aliases":["CVE-2026-50276"],"modified":"2026-07-15T23:26:43.018507Z","published":"2026-07-15T23:07:49Z","database_specific":{"severity":"HIGH","github_reviewed":true,"github_reviewed_at":"2026-07-15T23:07:49Z","nvd_published_at":null,"cwe_ids":["CWE-400","CWE-770"]},"references":[{"type":"WEB","url":"https://github.com/DataDog/dd-trace-rb/security/advisories/GHSA-p5f6-rccc-jv98"},{"type":"PACKAGE","url":"https://github.com/DataDog/dd-trace-rb"}],"affected":[{"package":{"name":"datadog","ecosystem":"RubyGems","purl":"pkg:gem/datadog"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.32.0"}]}],"versions":["2.0.0","2.0.0.beta1","2.0.0.beta2","2.0.0.rc1","2.1.0","2.10.0","2.11.0","2.12.0","2.12.1","2.12.2","2.13.0","2.14.0","2.15.0","2.16.0","2.17.0","2.18.0","2.19.0","2.2.0","2.20.0","2.21.0","2.22.0","2.23.0","2.24.0","2.25.0","2.26.0","2.27.0","2.28.0","2.29.0","2.3.0","2.30.0","2.31.0","2.4.0","2.5.0","2.6.0","2.7.0","2.7.1","2.8.0","2.9.0"],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-p5f6-rccc-jv98/GHSA-p5f6-rccc-jv98.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"}]}