Quick answers
- Is CVE-2026-39197 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39197 being exploited in the wild.
- How severe is CVE-2026-39197?
- Informational severity, with a CVSS score of 7.5, published 15 June 2026.
- Which products and versions are affected?
- Datadog Vector 0.54.0.
- Is there a fix for CVE-2026-39197?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-39197 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39197?
- Check whether you run Datadog Vector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Denial of Service vulnerability exists in Datadog Vector v0.54.0 due to improper resource management during the decompression and buffering of incoming requests. The affected components, including HTTP and gRPC ingest paths (such as OpenTelemetry HTTP and Splunk HEC), collect and decompress request bodies into memory before enforcing configured size limits. An attacker can exploit this by sending 'zip bombs' or oversized payloads that cause the process to exceed available memory, leading to an Out-of-Memory (OOM) termination or system unresponsiveness. The vulnerability is rooted in the /util/http/prelude.rs endpoint and related decompression helpers where the allocation boundary precedes the validation boundary.
Affected products
- Datadog Vector 0.54.0
Timeline
- 2026-06-13: other: Initial details shared via GitHub Gist
- 2026-06-15: disclosed: CVE published to NVD