CVE-2026-3172

8.1

pgvector · pgvector

A buffer overflow vulnerability in the parallel HNSW index build process of pgvector allows authenticated database users to leak sensitive information or crash the database server.

Executive summary

A buffer overflow in the pgvector extension for PostgreSQL presents a significant risk of data exposure and service disruption for database environments.

Vulnerability

This vulnerability involves integer wraparound and out-of-bounds write flaws (CWE-191 and CWE-787) within the parallel HNSW index build function. The issue requires the attacker to have at least low-level database user privileges to trigger the overflow condition.

Business impact

The ability for a database user to leak sensitive data from other relations poses a severe threat to data confidentiality and regulatory compliance. Furthermore, the potential for a service crash introduces significant availability risks. With a CVSS score of 8.1, this vulnerability is classified as High, reflecting the potential for unauthorized data access and denial of service.

Remediation

Immediate Action: Update the pgvector extension to version 0.8.2 or later to incorporate the vendor security patches.

Proactive Monitoring: Audit database user permissions to ensure the principle of least privilege is enforced, and monitor PostgreSQL logs for unexpected process crashes or recurring index build errors.

Compensating Controls: Restrict the ability to create HNSW indexes to trusted database roles only, and monitor for unusual query patterns that might indicate an attempt to trigger index-building operations for exploitation.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the potential for sensitive data exfiltration, organizations utilizing the pgvector extension must prioritize the upgrade to version 0.8.2. Administrators should verify their current extension version immediately and schedule maintenance windows to apply the necessary patches, thereby neutralizing the risk of unauthorized data access and potential server instability.

More pgvector CVEs

Sources

Originally found and disclosed by Thanks to chungkn from OneMount Group for reporting this., per the CVE Program record.