Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-50273 high CVSS 7.5

Vulnerability in Datadog.Trace (CVE-2026-50273)

Summary

Vulnerability in Datadog.Trace (CVE-2026-50273). Risk of unauthorized operations or information disclosure. Exploitable via baggage. Mitigation: upgrade to 3.43.0 or later.

Original description

The description as published by the source.

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 upst…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-50273 has been found in Datadog.Trace.
Attackers can target a specific entry point like baggage over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Datadog.Trace to 3.43.0 or later.
If unsure, ask your IT team or search "Datadog.Trace CVE-2026-50273" on the vendor's site.

CVE-2026-50273 (Datadog.Trace) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: baggage / DD_TRACE_PROPAGATION_STYLE / DD_TRACE_PROPAGATION_STYLE_EXTRACT / LimitRequestFieldSize
Patched: 3.43.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in Datadog.Trace. Attackers reach the vulnerable code path via baggage without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Datadog.Trace. Attack surface: baggage / DD_TRACE_PROPAGATION_STYLE / DD_TRACE_PROPAGATION_STYLE_EXTRACT / LimitRequestFieldSize.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.43.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Datadog.Trace' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Datadog.Trace' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Datadog.Trace を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Datadog.Trace to 3.43.0

    ステージング環境で 3.43.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget Datadog.Trace
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.43.0"}]}]
nuget Datadog.Trace.OpenTracing
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.43.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details