EUVD-2026-67829
GHSA-gpwf-4h98-v82q
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Default network-accessible tracecontext parsing requires no auth or complexity; sole impact is availability exhaustion with no confidentiality or integrity loss.
Primary rating from Vendor (https://github.com/DataDog/dd-trace-rs).
CVSS VectorVendor: https://github.com/DataDog/dd-trace-rs
Lifecycle Timeline
3DescriptionCVE.org
Impact
Datadog tracing libraries that implement W3C Trace Context (tracecontext) propagation parse the incoming tracestate header without enforcing a size cap on the Datadog vendor entry (dd=...). The dd= value contains semicolon-separated key:value pairs, and the parser allocates a hash-map entry for each pair. A remote, unauthenticated attacker can send a tracestate header whose dd= member is arbitrarily large (or contains an arbitrarily large number of pairs), forcing unbounded CPU and memory consumption per request and enabling a remote Denial of Service. tracecontext extraction is enabled by default in affected tracers, so any internet-facing service instrumented with an affected version is exposed unless tracecontext has been explicitly removed from the propagation style configuration.
Patches
This is resolved in version 0.3.3 and later of the dd-trace-rs library.
Workarounds
If you cannot upgrade immediately:
- Disable
tracecontextextraction by settingDD_TRACE_PROPAGATION_STYLE_EXTRACTto a value that does not includetracecontext(for example,datadog). - Cap the maximum HTTP request header size at an upstream proxy or web server.
AnalysisAI
Unbounded W3C tracestate parsing in the datadog-opentelemetry Rust crate (dd-trace-rs) allows remote unauthenticated attackers to exhaust CPU and memory on any instrumented service by sending HTTP requests with an arbitrarily large or pair-dense dd= vendor entry in the tracestate header. Affected versions 0.1.0 through 0.3.2 are exposed under default configuration because tracecontext extraction is enabled without any opt-in, making every internet-facing Rust service using Datadog APM a viable target. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the target service is written in Rust, instrumented with the datadog-opentelemetry crate at version 0.1.0 through 0.3.2, and that tracecontext is present in the propagation extraction style - which is the default configuration, so no special operator misconfiguration is necessary. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.5 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is well-calibrated: the attack is network-reachable, requires no authentication or special complexity, and the only impact is availability, which aligns with a pure resource-exhaustion DoS. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | The primary remediation is upgrading datadog-opentelemetry to version 0.3.3 or later, available at https://github.com/DataDog/dd-trace-rs/releases/tag/datadog-opentelemetry-v0.3.3; update the Cargo.toml dependency and rebuild the affected service. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Rust services using dd-trace-rs versions 0.1.0 through 0.3.2 and identify those exposed to the internet. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today