Quick answers
- Is CVE-2026-39196 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39196 being exploited in the wild.
- How severe is CVE-2026-39196?
- Informational severity, with a CVSS score of 0, published 15 June 2026.
- Which products and versions are affected?
- Datadog Vector 0.54.0.
- Is there a fix for CVE-2026-39196?
- 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-39196 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-39196?
- 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 SQL injection vulnerability exists in Datadog Vector v0.54.0 within the ClickHouse sink's KeyPartitioner::partition function. The root cause is insufficient escaping of the 'database' template variable when constructing INSERT statements in the set_uri_query function. While the 'table' variable is escaped, the 'database' variable is inserted into the SQL string without similar sanitization. An attacker who can control event fields used in a database template can use crafted strings (e.g., using quotes and comments) to break out of the intended identifier context. This allows the attacker to redirect the INSERT operation to any ClickHouse table accessible by Vector's credentials, leading to data integrity issues or unauthorized data insertion.
Affected products
- Datadog Vector 0.54.0
Timeline
- 2026-06-13: other: Vulnerability details shared via GitHub Gist
- 2026-06-15: disclosed: CVE published