CVE-2026-3172 | pgvector buffer overflow in parallel HNSW index build

Buffer overflow in parallel HNSW index build in pgvector 0.6.0 through 0.8.1 allows a database user to leak sensitive data from other relations or crash the database server.

Published: 2026-02-25 Last update: 2026-04-15 Assigner: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-3172 is rated Low Risk (38.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-3172

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-29 0.04% 0.06% +0.01%
2 2026-02-26 — 0.04% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-3172

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.2 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Weakness enumeration for CVE-2026-3172

OS Trackers for CVE-2026-3172

vendor priority summary link
debian not yet assigned CVE-2026-3172 not yet assigned priority: Debian including 1 source packages (pgvector), 3 status rows across 3 suites (forky, sid, trixie): resolved 2, open 1. https://security-tracker.debian.org/tracker/CVE-2026-3172
redhat medium — https://access.redhat.com/security/cve/CVE-2026-3172
suse high CVE-2026-3172 severity important: SUSE including 15 source package names (pgvector-devel-0.8.2-1.1, pgvector-devel-0.8.2-150600.13.9.1, …), 27 product×package rows across 6 product lines (SUSE Linux Enterprise Module for Server Applications 15 SP7, SUSE Linux Enterprise Server 15 SP6-LTSS, … (6 product lines)): Fixed 20, First Fixed 7. https://www.suse.com/security/cve/CVE-2026-3172/
ubuntu medium CVE-2026-3172 medium priority: Ubuntu including 1 source packages (pgvector), 4 status rows across 4 suites (jammy, noble, questing, upstream): needs-triage 3, DNE 1. https://ubuntu.com/security/CVE-2026-3172

Affected software / configurations for CVE-2026-3172

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-3172

cvelogic Threat Intelligence