CVE-2026-18022

Awaiting Analysis Awaiting Analysis - Queue

Integer wraparound in pgvector index build allows out-of-bounds write

Publication date: 2026-07-29

Last updated on: 2026-07-31

Assigner: PostgreSQL

Description

Integer wraparound in IVFFlat index build in pgvector before 0.8.6 allows a database user to write data out-of-bounds, which could lead to arbitrary code execution. Only 32-bit systems are affected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-31

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-18022

Affected Vendors & Products

Vendor	Product	Version / Range
pgvector	pgvector	to 0.8.6 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.
CWE-190	The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

Executive Summary

This vulnerability is an integer wraparound issue in the IVFFlat index build process of pgvector before version 0.8.6. It allows a database user to write data out-of-bounds, potentially leading to arbitrary code execution. The flaw specifically affects 32-bit systems.

Detection Guidance

Detection requires checking the pgvector version installed on your system. Run 'pg_config --pgxs' or 'SELECT extversion FROM pg_extension WHERE extname = "vector";' in PostgreSQL to verify the version. If it is below 0.8.6 and you are on a 32-bit system, the system is vulnerable.

Impact Analysis

If you use pgvector on a 32-bit system with a version before 0.8.6, an attacker with database access could exploit this to execute arbitrary code. This could lead to data breaches, system compromise, or unauthorized access to sensitive information.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection principles or HIPAA's security requirements. Non-compliance may result in legal penalties, fines, or reputational damage.

Mitigation Strategies

Upgrade pgvector to version 0.8.6 or later immediately. If you are on a 32-bit system, consider migrating to a 64-bit system as a long-term solution. Ensure PostgreSQL is restarted after the upgrade to apply changes.

Hi! I’m here to help you understand CVE-2026-18022. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70