{"items":[{"id":"NVI-00016097","kind":"vulnerability","title":"dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-74j5-xf3v-crq8","CVE-2026-50274"],"plain_summary":"GitHub lists this reviewed advisory for github.com/DataDog/dd-trace-go, github.com/DataDog/dd-trace-go/v2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1f8fa0b6d6bb85e7cb4f0656c72a7027"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-15T23:05:20.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1f8fa0b6d6bb85e7cb4f0656c72a7027"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1f8fa0b6d6bb85e7cb4f0656c72a7027","url":"https://github.com/advisories/GHSA-74j5-xf3v-crq8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-74j5-xf3v-crq8","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T09:59:26.779Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1f8fa0b6d6bb85e7cb4f0656c72a7027"],"technology":"github.com/DataDog/dd-trace-go","known_exclusions":[],"conditions_summary":"### 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.8.1 and later of the `dd-trace-go` library.\n\n### Workarounds\nIf users cannot upgrade immediately:\n1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATIO","public_affected_ranges":["<= 1.24.1"]},{"certainty":"source_listed","source_ids":["sr-1f8fa0b6d6bb85e7cb4f0656c72a7027"],"technology":"github.com/DataDog/dd-trace-go/v2","known_exclusions":[],"conditions_summary":"### 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.8.1 and later of the `dd-trace-go` library.\n\n### Workarounds\nIf users cannot upgrade immediately:\n1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATIO","public_affected_ranges":["< 2.8.1"]}],"null_published_at":"2026-11-04T10:04:27.890Z","source_updated_at":"2026-07-15T23:05:20.000Z","source_disclosed_at":"2026-07-15T23:05:19.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-04T09:59:26.779Z"}],"next_cursor":null,"snapshot_revision":"42594"}