CVE-2026-18022

Published: Lug 29, 2026 Last Modified: Lug 30, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,8
Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: high

Description

AI Translation Available

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.

190

Integer Overflow or Wraparound

Stable
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Availability Integrity Confidentiality Access Control Other
Potential Impacts:
Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Memory) Dos: Instability Modify Memory Execute Unauthorized Code Or Commands Bypass Protection Mechanism Alter Execution Logic Dos: Resource Consumption (Cpu)
Applicable Platforms
Languages: Not Language-Specific, C
Likelihood of Exploit: Medium
View CWE Details
787

Out-of-bounds Write

Draft
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Integrity Availability Other
Potential Impacts:
Modify Memory Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart Unexpected State
Applicable Platforms
Languages: Memory-Unsafe, C, C++, Assembly
Technologies: ICS/OT
Likelihood of Exploit: High
View CWE Details
https://github.com/pgvector/pgvector/commit/636a92a3395d2e0…
https://github.com/pgvector/pgvector/commit/636a92a3395d2e036ffd40d07aeb400a708…
https://github.com/pgvector/pgvector/issues/1006
https://github.com/pgvector/pgvector/issues/1006