CVE-2026-103484

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-91044 (ENISA EUVD) · GHSA-pw7q-9788-x566 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 1, 2026

Last Modified

October 2, 2026

Advisory Details (2)

Auto-updated Oct 1, 2026
Patch available. 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/ee00d39ab30c2a7cf9510abf9288c624d91db156
Web page

Buffer overflow with IVFFlat index build · Issue #1036 · pgvector/pgvector · GitHub

https://github.com/pgvector/pgvector/issues/1036

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpostgresql16-pgvector-0:0.8.7-1.el10_02026-11-05redhat
redhatpostgresql:16-9060020261027113619.rhel92026-11-02redhat
redhatpostgresql18-pgvector-0:0.8.7-1.el10_22026-10-22redhat
redhatpostgresql16-pgvector-0:0.8.7-1.el10_22026-10-22redhat
redhatpostgresql:16-9080020261012122334.rhel92026-10-20redhat
redhatpostgresql:18-9080020261012122438.rhel92026-10-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pgvector0.8.0-1 ... 0.8.7-1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pgvector0.8.0-1 ... 0.8.6-1 (8 versions)
  • every version up to 0.8.7-1: fixed in 0.8.7-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-11-07 23:51 UTCEchelonGraph re-scored
  8. 2026-11-07 23:51 UTCVendor advisory
  9. 2026-11-07 23:51 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-31 21:34 UTCEchelonGraph re-scored
  18. 2026-10-31 21:34 UTCVendor advisory
  19. 2026-10-31 21:34 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 69 more
  1. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-25 14:56 UTCEchelonGraph re-scored
  3. 2026-10-24 21:59 UTCEchelonGraph re-scored
  4. 2026-10-24 21:59 UTCVendor advisory
  5. 2026-10-24 21:59 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-18 05:09 UTCEchelonGraph re-scored
  14. 2026-10-17 19:43 UTCEchelonGraph re-scored
  15. 2026-10-17 19:43 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-12 16:40 UTCEchelonGraph re-scored
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-11 20:15 UTCEchelonGraph re-scored
  24. 2026-10-11 18:01 UTCEchelonGraph re-scored
  25. 2026-10-11 18:01 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-11 15:01 UTCEchelonGraph re-scored
  27. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-10-11 06:36 UTCEchelonGraph re-scored
  29. 2026-10-11 06:36 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-10-10 19:17 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  32. 2026-10-10 07:55 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-10-09 20:37 UTCEchelonGraph re-scored
  34. 2026-10-09 20:37 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-10-09 09:20 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  37. 2026-10-08 22:02 UTCEchelonGraph re-scored
  38. 2026-10-08 22:01 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-10-08 10:43 UTCEchelonGraph re-scored
  41. 2026-10-08 10:43 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-10-07 23:22 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-10-07 12:03 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-10-07 00:46 UTCEchelonGraph re-scored
  46. 2026-10-07 00:45 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  47. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-10-06 13:25 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-10-06 02:08 UTCEchelonGraph re-scored
  50. 2026-10-06 02:08 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-10-05 14:46 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  53. 2026-10-05 03:29 UTCEchelonGraph re-scored
  54. 2026-10-05 03:29 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  55. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-10-04 16:11 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  57. 2026-10-04 04:52 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-03 17:35 UTCEchelonGraph re-scored
  59. 2026-10-03 17:35 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  61. 2026-10-03 06:18 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  62. 2026-10-02 19:00 UTCEchelonGraph re-scored
  63. 2026-10-02 19:00 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  64. 2026-10-02 07:48 UTCEchelonGraph re-scored
  65. 2026-10-02 07:47 UTCGHSA enrichmentGHSA-pw7q-9788-x566 · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-10-01 20:28 UTCEchelonGraph re-scored
  67. 2026-10-01 20:01 UTCEchelonGraph re-scored
  68. 2026-10-01 19:56 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  69. 2026-10-01 19:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-103484?
CVE-2026-103484 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-103484 published?
The CVE record for CVE-2026-103484 was published on October 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
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 (37th 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?
A fix for CVE-2026-103484 is available: update to the fixed version the vendor names in its advisory. 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

Explore →

Is Your Infrastructure Affected by CVE-2026-103484?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.