CVE-2026-2003VulnerabilityPublished 12 Feb 2026

CVE-2026-2003: PostgreSQL · Improper Validation of Specified Type of Input

Affects PostgreSQLSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 18.2 : update PostgreSQL when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.2, 17.8, 16.12 +2

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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 to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
PostgreSQL	Affected >=18 <18.2 >=17 <17.8 >=16 <16.12 >=15 <15.16 <14.21	Fixed in 18.2 17.8 16.12 15.16 14.21

AI-suggested

Organizations should promptly upgrade affected PostgreSQL instances to the fixed versions: 18.2, 17.8, 16.12, 15.16, or 14.21 or later. If you cannot patch yet, restrict database access to trusted users only and enforce the principle of least privilege to minimize the number of users who can exploit this vulnerability. Monitor database logs for unusual queries or access patterns involving the 'oidvector' type or suspicious input data. Employ network segmentation and firewall rules to limit external access to PostgreSQL servers. Consider implementing database activity monitoring solutions to detect anomalous behavior. If patching is delayed, review application code and database roles to ensure that untrusted users cannot execute queries involving the vulnerable input type. Regularly audit user privileges and rotate credentials to reduce the risk of compromised accounts being used to exploit this flaw. Stay informed through official PostgreSQL security advisories for any additional guidance or patches.

Description

Improper validation of type "oidvector" in PostgreSQL allows a database user to disclose a few bytes of server memory. We have not ruled out viability of attacks that arrange for presence of confidential information in disclosed bytes, but they seem unlikely. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

Impact

The primary impact of CVE-2026-2003 is the potential leakage of small amounts of server memory to authenticated database users. While the disclosed memory bytes may not consistently contain sensitive information, there is a non-zero risk that confidential data could be exposed, which could aid attackers in further reconnaissance or exploitation efforts. This could lead to partial compromise of data confidentiality within affected PostgreSQL databases. The vulnerability does not affect data integrity or availability, and exploitation requires authenticated access, limiting the attack surface to internal or trusted users or attackers who have already gained database credentials. Organizations relying on PostgreSQL for critical data storage, especially those with multi-tenant environments or sensitive information, may face increased risk of data leakage. The medium severity rating reflects these factors. Since PostgreSQL is widely used globally in enterprise, cloud, and open-source applications, the impact could be significant if left unpatched, particularly in environments with less stringent access controls.

References

postgresql.org/support/security/CVE-2026-2003/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Feb 2026, 14:15 UTC

Technical details

References

Community reviews

Related threats