CVE-2026-39196
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDatadog, Inc Vector v0.54.0 was discovered to contain a SQL injection vulnerability in the set_uri_query parameter in the KeyPartitioner::partition function. This vulnerability allows attackers to access sensitive database information via crafted SQL statements.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in Datadog Vector v0.54.0 in the KeyPartitioner::partition function's set_uri_query parameter allows attackers to inject malicious SQL statements and access sensitive database information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Datadog Vector installation and versionRun 'vector --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l vector', 'rpm -qi vector', or 'brew list vector')Affected if The installed version is 0.54.0
-
Locate Vector configuration filesCheck common Vector config locations such as /etc/vector/, /etc/vector.yaml, /etc/vector.d/, or the path specified by the VECTOR_CONFIG environment variableAffected if Vector configuration files exist in the environment
-
Search for KeyPartitioner usage in configurationGrep for 'KeyPartitioner' or 'key_partitioner' in all configuration files (e.g., grep -r 'KeyPartitioner' /etc/vector/ or grep -r 'key_partitioner' .)Affected if The KeyPartitioner component is configured in any pipeline
-
Inspect set_uri_query parameter usageIf KeyPartitioner is found, examine the configuration block for the set_uri_query parameter and its value; verify whether user-controlled or dynamic input is being passed to this parameterAffected if The set_uri_query parameter is present and contains unsanitized or dynamic input that could be exploited for SQL injection
-
Check for database sink configurations using partitioned dataReview any sink configurations that connect to databases (SQL, MySQL, PostgreSQL, etc.) and verify if they consume partitioned data from KeyPartitioner with set_uri_query enabledAffected if Database sinks are configured to use partitioned data from KeyPartitioner with set_uri_query
A user is affected if Vector version 0.54.0 is running AND the KeyPartitioner component is configured with the set_uri_query parameter pointing to a database sink.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of Vector. If no patch is available, implement strict input validation and parameterized queries on the set_uri_query parameter to prevent SQL injection, and restrict database access permissions as a defense-in-depth measure.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data