IVFFlat index build in pgvector before 0.8.7 allows a database user to write data out-of-bounds, which can lead to arbitrary code execution.
CVE-2026-103484
HIGHPre-NVD 8.88.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-01. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG Risk 40/100CISA SSVC
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%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 1, 2026
Last Modified
October 2, 2026
Advisory Details (2)
Auto-updated Oct 1, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit
commit ee00d39ab30c (pgvector/pgvector)
Fix landed in pgvector/pgvector commit ee00d39ab30c — awaiting tagged release
https://github.com/pgvector/pgvector/commit/ee00d39ab30c2a7cf9510abf9288c624d91db156generic
Buffer overflow with IVFFlat index build · Issue #1036 · pgvector/pgvector · GitHub
https://github.com/pgvector/pgvector/issues/1036Vendor Advisories for CVE-2026-103484(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pgvector | 0.8.0-1 ... 0.8.7-1 (9 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pgvector | 0.8.0-1 ... 0.8.6-1 (8 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× 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-10-05 03:29 UTCEG score recompute
- 2026-10-05 03:29 UTCGHSA enrichment
- 2026-10-04 23:21 UTCEPSS rescore
- 2026-10-04 16:11 UTCGHSA enrichment
- 2026-10-04 04:52 UTCGHSA enrichment
- 2026-10-03 17:35 UTCEG score recompute
- 2026-10-03 17:35 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 06:18 UTCGHSA enrichment
- 2026-10-02 19:00 UTCEG score recompute
- 2026-10-02 19:00 UTCGHSA enrichment
- 2026-10-02 07:48 UTCEG score recompute
- 2026-10-02 07:47 UTCGHSA enrichment
- 2026-10-01 20:28 UTCEG score recompute
- 2026-10-01 20:01 UTCEG score recompute
- 2026-10-01 19:56 UTCEG score recompute
- 2026-10-01 19:55 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-103484?
CVE-2026-103484 is a high vulnerability published on October 1, 2026. IVFFlat index build in pgvector before 0.8.7 allows a database user to write data out-of-bounds, which can lead to arbitrary code execution.
When was CVE-2026-103484 disclosed?
CVE-2026-103484 was first published on October 1, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103484 actively exploited?
CVE-2026-103484 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103484?
CVE-2026-103484 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103484?
An upstream fix for CVE-2026-103484 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-103484 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-103484
Is Your Infrastructure Affected by CVE-2026-103484?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.