CVE-2026-3172
Buffer overflow in pgvector HNSW index build enables data leakage or DB crash.
Is CVE-2026-3172 being exploited?
Not confirmed. CVE-2026-3172 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-3172?
CVE-2026-3172 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3172?
Not known from our data. No patch reference has been recorded for CVE-2026-3172, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-3172 affect?
CVE-2026-3172 affects PostgreSQL with pgvector extension (versions 0.6.0–0.8.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3172?
Upgrade pgvector to a fixed version when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated DB user can leak sensitive data from other relations or crash the database during parallel HNSW index builds.
Patch when possible
- affected>= 0.8.0 and < 0.8.2
- affected0.7.0
- affected0.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.