PatchSiren cyber security CVE debrief
CVE-2026-50273 DataDog CVE debrief
CVE-2026-50273 is a vulnerability in Datadog .NET Tracer that allows remote unauthenticated attackers to cause unbounded CPU and memory consumption. The issue is fixed in version 3.43.0. The vulnerability affects Datadog .NET Tracer prior to version 3.43.0 and has a high CVSS score of 7.5. The vulnerability is related to the parsing of incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on extraction.
- Vendor
- DataDog
- Product
- dd-trace-dotnet
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-17
- Original CVE updated
- 2026-07-17
- Advisory published
- 2026-07-17
- Advisory updated
- 2026-07-17
Who should care
Users of Datadog .NET Tracer prior to version 3.43.0 should be aware of this vulnerability and take steps to mitigate it. This includes operators, platform administrators, vulnerability management teams, and security teams who need to assess the impact of the vulnerability on their systems and plan for remediation.
Technical summary
Datadog .NET Tracer is a client library for Datadog APM for .NET applications. Prior to 3.43.0, 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 on extraction, allowing a remote unauthenticated attacker to send a baggage header with many comma-separated key-value pairs or one very large value and cause unbounded CPU and memory consumption in services with baggage propagation enabled. The issue is fixed in version 3.43.0.
Defensive priority
High
Recommended defensive actions
- Update to version 3.43.0 or later
- Monitor for suspicious activity
- Implement compensating controls
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record was published on 2026-07-17T18:17:16.840Z and has not been modified since then. The NVD entry is currently Awaiting Analysis. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The CVE record does not provide details on the vulnerability's impact or exploitability.
Official resources
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-17T18:17:16.840Z and has not been modified since then.