CVE-2026-50274

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

Published Jul 17, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Datadog dd-trace-go is a Go client library for Datadog application performance monitoring, profiling, and security monitoring. Prior to 2.8.1, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES limits on the extract path. 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, causing unbounded CPU and memory consumption and enabling a remote denial of service against HTTP services with baggage propagation enabled. This issue is fixed in version 2.8.1.

Analysis

AI-generated

Technical impact

The dd-trace-go library, a Go client for Datadog monitoring, was vulnerable before version 2.8.1. It parsed incoming W3C baggage headers without enforcing the DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES limits in the extraction path. An attacker could send a request whose baggage header contained an arbitrarily large number of comma-separated key-value pairs or a single very large value, causing the library to consume unbounded CPU cycles and memory. This led to a remote denial of service against any HTTP service that processes baggage propagation. The issue was fixed in version 2.8.1.

Affected Systems

The DataDog client library, versions prior to 2.8.1, is affected. The library is used for application performance monitoring, profiling, and security monitoring.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.5 and an EPSS score of < 1%. It is not listed in CISA KEV. A remote, unauthenticated attacker can exploit the issue by sending a crafted HTTP request with a large baggage header. While the exploit requires network access to a service that integrates dd-trace-go, the lack of input validation makes it easy to trigger, resulting in high CPU and memory consumption.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the DataDog dd-trace-go library to version 2.8.1 or later to apply the fix.
  • If an upgrade is not immediately possible, set environment variables DD_TRACE_BAGGAGE_MAX_ITEMS and DD_TRACE_BAGGAGE_MAX_BYTES to enforce limits on baggage header size.
  • Monitor services for unusually large baggage headers, high CPU usage, or abnormal memory consumption to detect potential exploitation.

Generated by OpenCVE AI on July 30, 2026 at 23:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-74j5-xf3v-crq8 dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Datadog
Datadog dd-trace-java
Vendors & Products Datadog
Datadog dd-trace-java
Type Values Removed Values Added
Description Datadog dd-trace-go is a Go client library for Datadog application performance monitoring, profiling, and security monitoring. Prior to 2.8.1, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES limits on the extract path. 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, causing unbounded CPU and memory consumption and enabling a remote denial of service against HTTP services with baggage propagation enabled. This issue is fixed in version 2.8.1.
Title dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
Weaknesses CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 3:04 PM
Reserved
Jun 4, 2026, 4:26 PM
Status
Awaiting Analysis
Published
Jul 17, 2026, 9:17 PM
Modified
Oct 24, 2026, 8:10 PM
Severity
Important
Public date
Jul 17, 2026, 8:41 PM