Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS

CVE-2026-50274GHSA-74j5-xf3v-crq8

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/DataDog/dd-trace-go

    Affected
    <= 1.24.1
    Fixed in
    no fixed version recorded

  • Go github.com/DataDog/dd-trace-go/v2

    Affected
    < 2.8.1
    Fixed in
    2.8.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-50274: 0.79% estimated exploitation activity in the next 30 days; percentile 56.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 DDTRACEBAGGAGEMAXITEMS (default 64) and DDTRACEBAGGAGEMAXBYTES (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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-74j5-xf3v-crq8

  2. Revision 1 · created ·

    Published from osv record GO-2026-6000

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50274

Advisory: dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
IDs: CVE-2026-50274, GHSA-74j5-xf3v-crq8
Record: https://patchnext.com/advisories/cve-2026-50274 (revision 2, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/DataDog/dd-trace-go/v2 2.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/DataDog/dd-trace-go: affected <= 1.24.1
- Go github.com/DataDog/dd-trace-go/v2: affected < 2.8.1; fixed in 2.8.1

## Suggested inspection (read-only)
- Go github.com/DataDog/dd-trace-go: check the installed version with your package manager.
- Go github.com/DataDog/dd-trace-go/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/DataDog/dd-trace-go, github.com/DataDog/dd-trace-go/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6000 (OSV record GO-2026-6000 lists affected ranges: Go github.com/DataDog/dd-trace-go >=0; Go github.com/DataDog/dd-trace-go/v2 >=0 <2.8.1 (fixed))
- Verified: https://github.com/advisories/GHSA-74j5-xf3v-crq8 (GitHub-reviewed advisory GHSA-74j5-xf3v-crq8 lists affected ranges: Go github.com/DataDog/dd-trace-go >=0 =0 <2.8.1)

Commands are suggestions: review each one before running it.

Loading voting…