# CVE-2026-3172: pgvector buffer overflow in parallel HNSW index build > A buffer overflow in pgvector's parallel HNSW index build allows database users to leak sensitive data or crash the server. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 25 Feb 2026 - **Updated:** 26 Feb 2026 - **Also known as:** DEBIAN-CVE-2026-3172, ECHO-6b5c-756e-cda5, GHSA-789c-mgqf-5hwx, SUSE-SU-2026:1068-1, SUSE-SU-2026:21153-1, UBUNTU-CVE-2026-3172, openSUSE-SU-2026:10409-1, openSUSE-SU-2026:20489-1 ## What is CVE-2026-3172? CVE-2026-3172 is a high-severity memory corruption vulnerability in pgvector, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Buffer overflow in parallel HNSW index build in pgvector 0.6.0 through 0.8.1 allows a database user to leak sensitive data from other relations or crash the database server. Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound)) ## Which versions are affected by CVE-2026-3172? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pgvector` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 0.8.2-150600.13.9.1 | | `postgresql16-pgvector` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 0.8.2-150600.13.9.1 | | `postgresql17-pgvector` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 0.8.2-150600.13.9.1 | | `postgresql18-pgvector` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 0.8.2-150600.13.9.1 | | `pgvector` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 0.8.2-150600.13.9.1 | | `postgresql16-pgvector` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 0.8.2-150600.13.9.1 | | `postgresql17-pgvector` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 0.8.2-150600.13.9.1 | | `postgresql18-pgvector` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 0.8.2-150600.13.9.1 | | `pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql13-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql14-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql15-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql16-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql17-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql18-pgvector` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.8.2-160000.1.1 | | `pgvector` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql16-pgvector` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql17-pgvector` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql18-pgvector` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 0.8.2-150600.13.9.1 | | `pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql13-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql14-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql15-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql16-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql17-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql18-pgvector` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.8.2-160000.1.1 | | `pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql13-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql14-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql15-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql16-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql17-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `postgresql18-pgvector` | openSUSE:Leap 15.6 | All versions | 0.8.2-150600.13.9.1 | | `pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql13-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql14-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql15-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql16-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql17-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | | `postgresql18-pgvector` | openSUSE:Leap 16.0 | All versions | 0.8.2-160000.1.1 | ## How do I fix CVE-2026-3172? Upgrade to a fixed version. ## Is CVE-2026-3172 being exploited? There is no known exploitation of CVE-2026-3172 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-3172 and fix it if it is affected. What it is: CVE-2026-3172 is a high-severity memory corruption vulnerability in pgvector, published on 25 Feb 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-3172 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-3172/ (Markdown: https://insights.sbomify.com/CVE-2026-3172/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3172 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3172 - OSV: https://osv.dev/vulnerability/CVE-2026-3172 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-3172/ Summaries are generated and may contain mistakes; the official description above is the record.