CVE-2026-18022
Integer wrap in pgvector IVFFlat index allows OOB write and possible RCE on 32-bit systems.
Is CVE-2026-18022 being exploited?
Not confirmed. CVE-2026-18022 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-18022?
CVE-2026-18022 is rated High with a CVSS score of 8.8. 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-18022?
Yes. A fix has been recorded for CVE-2026-18022. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-18022 affect?
CVE-2026-18022 affects pgvector < 0.8.6, PostgreSQL with pgvector on 32-bit OSes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18022?
Upgrade pgvector to >= 0.8.6 or avoid building IVFFlat indexes on 32-bit systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A local database user can trigger an integer wrap during IVFFlat index build to write OOB, enabling arbitrary code execution as the DB process user on 32-bit hosts.
Patch when possible
- affected< 0.8.6
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.