# CVE-2026-103484: pgvector buffer overflow in IVFFlat index build > A database user can trigger a buffer overflow during IVFFlat index build in pgvector, potentially leading to arbitrary code execution. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Oct 2026 - **Updated:** 1 Oct 2026 - **Also known as:** ALSA-2026:85791, ALSA-2026:85814, ALSA-2026:88359, ALSA-2026:88360, DEBIAN-CVE-2026-103484, ECHO-8baa-daff-36fe, GHSA-pw7q-9788-x566, RHSA-2026:85791, RHSA-2026:85814, RLSA-2026:85791, RLSA-2026:85814, RLSA-2026:88359, RLSA-2026:88360, SUSE-SU-2026:24211-1, SUSE-SU-2026:4804-1, UBUNTU-CVE-2026-103484, openSUSE-SU-2026:12067-1, openSUSE-SU-2026:22065-1 ## What is CVE-2026-103484? CVE-2026-103484 is a high-severity memory corruption vulnerability in pgvector, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-787 (Out-of-bounds Write), CWE-1284 (Improper Validation of Specified Quantity in Input) ## Which versions are affected by CVE-2026-103484? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pgvector` | AlmaLinux:10 | All versions | 0.8.7-1.el10_2 | | `postgresql18-pgvector` | AlmaLinux:10 | All versions | 0.8.7-1.el10_2 | | `pg_repack` | AlmaLinux:9 | All versions | 1.5.1-1.module_el9.6.0+146+c54fdeca | | `pg_repack` | AlmaLinux:9 | All versions | 1.5.3-1.module_el9.8.0+234+5456f35d | | `pgaudit` | AlmaLinux:9 | All versions | 16.0-1.module_el9.4.0+66+eb9878bc | | `pgaudit` | AlmaLinux:9 | All versions | 18.0-1.module_el9.8.0+234+5456f35d | | `pgvector` | AlmaLinux:9 | All versions | 0.8.7-1.module_el9.8.0+324+0cb93d9d | | `pgvector` | AlmaLinux:9 | All versions | 0.8.7-1.module_el9.8.0+325+9e644128 | | `postgis` | AlmaLinux:9 | All versions | 3.5.3-6.module_el9.8.0+311+c39b793b | | `postgis` | AlmaLinux:9 | All versions | 3.6.1-4.module_el9.8.0+310+22372bcc | | `postgis-client` | AlmaLinux:9 | All versions | 3.5.3-6.module_el9.8.0+311+c39b793b | | `postgis-client` | AlmaLinux:9 | All versions | 3.6.1-4.module_el9.8.0+310+22372bcc | | `postgis-docs` | AlmaLinux:9 | All versions | 3.5.3-6.module_el9.8.0+311+c39b793b | | `postgis-docs` | AlmaLinux:9 | All versions | 3.6.1-4.module_el9.8.0+310+22372bcc | | `postgis-upgrade` | AlmaLinux:9 | All versions | 3.5.3-6.module_el9.8.0+311+c39b793b | | `postgis-upgrade` | AlmaLinux:9 | All versions | 3.6.1-4.module_el9.8.0+310+22372bcc | | `postgis-utils` | AlmaLinux:9 | All versions | 3.5.3-6.module_el9.8.0+311+c39b793b | | `postgis-utils` | AlmaLinux:9 | All versions | 3.6.1-4.module_el9.8.0+310+22372bcc | | `postgres-decoderbufs` | AlmaLinux:9 | All versions | 2.4.0-1.Final.module_el9.4.0+66+eb9878bc | | `postgres-decoderbufs` | AlmaLinux:9 | All versions | 3.3.1-1.Final.module_el9.8.0+234+5456f35d | | `postgresql` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-contrib` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-contrib` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-docs` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-docs` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-plperl` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-plperl` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-plpython3` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-plpython3` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-pltcl` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-pltcl` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-private-devel` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-private-devel` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-private-libs` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-private-libs` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-server` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-server` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | | `postgresql-server-devel` | AlmaLinux:9 | All versions | 16.15-1.module_el9.8.0+311+c39b793b | | `postgresql-server-devel` | AlmaLinux:9 | All versions | 18.6-1.module_el9.8.0+310+22372bcc | ## How do I fix CVE-2026-103484? Upgrade to a fixed version. ## Is CVE-2026-103484 being exploited? There is no known exploitation of CVE-2026-103484 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-103484 and fix it if it is affected. What it is: CVE-2026-103484 is a high-severity memory corruption vulnerability in pgvector, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-103484 in the wild and no public exploit code. Affected product: pgvector. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-103484/ (Markdown: https://insights.sbomify.com/CVE-2026-103484/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103484 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103484 - OSV: https://osv.dev/vulnerability/CVE-2026-103484 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-103484/ Summaries are generated and may contain mistakes; the official description above is the record.