https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T16:37:18.330007+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-338591 EUVD-2026-338591 2026-10-06T16:37:18.393754+00:00 EUVD-2026-338591 https://cve.radiocsirt.org/vuln/fkie_cve-2026-50273 fkie_cve-2026-50273 2026-10-06T16:37:18.393793+00:00

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. This issue is fixed in version 3.43.0.

 https://cve.radiocsirt.org/vuln/ghsa-38wr-vpc7-2mp4 GHSA-38wr-vpc7-2mp4 — dd-trace-dotnet: Improper parsing of W3C baggage headers may lead to DoS 2026-10-06T16:37:18.393828+00:00

Affected: NuGet: Datadog.Trace, NuGet: Datadog.Trace.OpenTracing

### Impact Datadog 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. The 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.

### Patches This is resolved in version 3.43.0 and later of the `dd-trace-dotnet` library.

### Workarounds If users cannot upgrade immediately: 1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATION_STYLE` (or `DD_TRACE_PROPAGATION_STYLE_EXTRACT` if set independently). 2. 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`).

### Resources Related up…