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.
CVE-2026-18022
HIGHPre-NVD 8.88.8
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 29, 2026
Advisory Details (2)
Auto-updated Jul 29, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit
commit 636a92a3395d (pgvector/pgvector)
Fix landed in pgvector/pgvector commit 636a92a3395d — awaiting tagged release
https://github.com/pgvector/pgvector/commit/636a92a3395d2e036ffd40d07aeb400a708ae104generic
Buffer overflow with IVFFlat index build on 32-bit systems · Issue #1006 · pgvector/pgvector · GitHub
https://github.com/pgvector/pgvector/issues/1006Vendor Advisories for CVE-2026-18022(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 20:21 UTCEG score recompute
- 2026-07-29 20:01 UTCEG score recompute
- 2026-07-29 19:24 UTCEG score recompute
- 2026-07-29 19:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-787
Frequently asked(4)
What is CVE-2026-18022?
CVE-2026-18022 is a high vulnerability published on July 29, 2026. 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.
When was CVE-2026-18022 disclosed?
CVE-2026-18022 was first published in the National Vulnerability Database on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-18022?
CVE-2026-18022 has a CVSS v3 base score of 8.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-18022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18022, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18022
Is Your Infrastructure Affected by CVE-2026-18022?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.