VulnerabilityPublished 25 Feb 2026

CVE-2026-3172: pgvector · Integer Underflow or Wraparound

Affects pgvectorSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 0.8.2 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.8.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade pgvector to 0.8.2.

Affected software

Product	Affected	Fixed in
pgvector	Affected >=0.8.0 <0.8.2 =0.7.0 =0.6.0	Fixed in 0.8.2
GitHubpgvector/pgvector`pkg:github/pgvector/pgvector`Other threats	Affected =0.6.0 =0.7.0 =0.8.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade pgvector to the latest patched version once it is released by the maintainers to address CVE-2026-3172.
If you cannot patch yet, restrict database user privileges to the minimum necessary, especially limiting access to pgvector features and the ability to build or rebuild HNSW indexes.
Monitor database logs and audit trails for unusual activity related to index builds or access patterns that could indicate exploitation attempts.
Implement network segmentation and firewall rules to limit access to PostgreSQL servers running pgvector, reducing exposure to untrusted users.
Consider disabling parallel HNSW index builds if configurable, or temporarily avoid using pgvector for vector similarity searches in sensitive environments.
Conduct internal penetration testing and code reviews focusing on pgvector usage to identify potential exploitation vectors.
Educate database administrators and developers about this vulnerability and the importance of applying updates promptly.
Employ runtime protections such as memory safety tools or database activity monitoring solutions to detect and prevent buffer overflow exploitation attempts.

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.

Impact

The vulnerability allows an attacker with limited database privileges to leak sensitive data from other database relations, breaching confidentiality boundaries within the PostgreSQL environment. This can lead to unauthorized data disclosure, potentially exposing sensitive business or personal information. Additionally, the buffer overflow can cause the database server to crash, resulting in denial of service and impacting availability of critical applications relying on PostgreSQL and pgvector. Organizations using pgvector for AI/ML workloads or vector similarity search may face operational disruptions and data breaches. The attack can be launched remotely over the network without user interaction, increasing the risk of exploitation in multi-tenant or cloud environments. The scope includes all systems running vulnerable versions of pgvector, which may be widespread given the growing adoption of vector search extensions. The impact on integrity is low as the vulnerability does not allow data modification. However, the combined confidentiality and availability impacts make this a significant threat to database security and service continuity.

References

github.com/pgvector/pgvector/issues/959 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Mar 2026, 11:29 UTC

Technical details

References

Community reviews

Related threats