Security readout for executives and security teams
Plain-English summary
CVE-2026-3172 affects pgvector, a PostgreSQL extension. A database user with access could trigger a flaw during parallel HNSW index building, potentially exposing sensitive data from other database relations or crashing the database server. This is high priority where pgvector is deployed and untrusted or broad database users can create indexes.
Executive priority
Treat as high priority for AI, search, or analytics systems using pgvector. The main business risks are unauthorized data exposure inside the database and service disruption. Prioritize systems with shared database access, multi-tenant workloads, or less-trusted database users.
Technical view
The CVE describes a buffer overflow in pgvector 0.6.0 through 0.8.1 during parallel HNSW index build. The assigned CVSS 3.1 score is 8.1: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality and availability impact and no integrity impact. CWE mappings are CWE-191 and CWE-787.
Likely exposure
Exposure is likely limited to PostgreSQL environments using pgvector versions 0.6.0 through 0.8.1, especially where database users can build HNSW indexes. Systems without pgvector or without affected versions are not indicated as affected by the provided sources.
Exploitation context
The CVE states exploitation requires a database user. The reported outcomes are sensitive data leakage from other relations or database server crash. The source bundle does not indicate active exploitation, and the CVE is not listed as KEV in the provided data.
Researcher notes
Evidence is limited to the CVE record and referenced pgvector issue. No public exploit status, fixed version, or official mitigation is provided in the source bundle. Avoid assuming broad PostgreSQL impact; the issue is specifically described in pgvector parallel HNSW index builds.
Mitigation direction
- Inventory PostgreSQL instances for pgvector and record installed versions.
- Prioritize environments running pgvector 0.6.0 through 0.8.1.
- Review the referenced pgvector issue and vendor guidance for fixed releases or workarounds.
- Limit pgvector index-building privileges to trusted database users where feasible.
- Monitor affected databases for unexpected crashes until remediation is complete.
Validation and detection
- Confirm whether pgvector is installed on each PostgreSQL instance.
- Verify the installed pgvector version against 0.6.0 through 0.8.1.
- Identify roles permitted to create or rebuild HNSW indexes.
- Review recent database crash logs for unexplained failures during index builds.
- Track vendor issue status before closing remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-191: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H2.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pgvector/pgvector/issues/959CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.