CVE-2026-50274: dd-trace-go Denial of Service Vulnerability
HIGHCVE-2026-50274 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting dd-trace-go libraries in the Go ecosystem. The issue involves improper parsing of w3c baggage headers may lead to dos. Remediation is available by upgrading affected packages to version 2.8.1.
CVE-2026-50274 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-50274
To remediate this vulnerability, upgrade all affected dd-trace-go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/DataDog/dd-trace-go to Latest secure release
Upgrade github.com/DataDog/dd-trace-go/v2 to 2.8.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/DataDog/dd-trace-go
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-50274, inspect your project dependencies for dd-trace-go:
inspect dependencies for github.com/DataDog/dd-trace-go
Analyze the terminal output to locate any version of dd-trace-go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In dd-trace-go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-50274 Affected dd-trace-go Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/DataDog/dd-trace-go
|
Go |
≤ 1.24.1
|
|
|
github.com/DataDog/dd-trace-go/v2
|
Go |
< 2.8.1
|
2.8.1
|
References
Frequently Asked Questions
What is CVE-2026-50274?
Which dd-trace-go versions are affected?
What version fixes CVE-2026-50274?
Is github.com/DataDog/dd-trace-go affected?
Is github.com/DataDog/dd-trace-go/v2 affected?
What is the CVSS score of CVE-2026-50274?
What CWE is associated with CVE-2026-50274?
How can I check Go dependencies for CVE-2026-50274?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-74j5-xf3v-crq8",
"modified" : "2026-07-15T23:05:19Z",
"published" : "2026-07-15T23:05:19Z",
"aliases" : [ "CVE-2026-50274" ],
"summary" : "dd-trace-go: 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.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_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)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/DataDog/dd-trace-go"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.24.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/DataDog/dd-trace-go/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.8.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/DataDog/dd-trace-go/security/advisories/GHSA-74j5-xf3v-crq8"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/DataDog/dd-trace-go"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-15T23:05:19Z",
"nvd_published_at" : null
}
}