Bug 2501951 (CVE-2026-50274) - CVE-2026-50274 github.com/DataDog/dd-trace-go: Datadog dd-trace-go: Denial of Service via malicious baggage headers
Summary: CVE-2026-50274 github.com/DataDog/dd-trace-go: Datadog dd-trace-go: Denial of...
Keywords:
Status: NEW
Alias: CVE-2026-50274
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-17 21:03 UTC by OSIDB Bzimport
Modified: 2026-07-21 12:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-17 21:03:06 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.