PostgreSQL oidvector discloses a few bytes of memory
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.
- BDU:2026-01726
- ALSA-2026:19009
- ALSA-2026:19010
- DSA-6132-1
- DSA-6133-1
- openSUSE-SU-2026:10190-1
- openSUSE-SU-2026:10191-1
- openSUSE-SU-2026:10192-1
- openSUSE-SU-2026:10193-1
- openSUSE-SU-2026:10197-1
- openSUSE-SU-2026:20265-1
- openSUSE-SU-2026:20266-1
- openSUSE-SU-2026:20388-1
- openSUSE-SU-2026:20408-1
- openSUSE-SU-2026:20447-1
- RHSA-2026:19009
- RHSA-2026:19010
- RHSA-2026:3730
- RHSA-2026:3887
- RHSA-2026:3896
- Published
- Feb 12, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 20th percentile
- CWE
- CWE-1287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql14.0 and later · before 14.21
- postgresql postgresql15.0 and later · before 15.16
- postgresql postgresql16.0 and later · before 16.12
- postgresql postgresql17.0 and later · before 17.8
- postgresql postgresql18.0 and later · before 18.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.
n/a PostgreSQL
- 18 and later · before 18.2affected · rpm
- 17 and later · before 17.8affected · rpm
- 16 and later · before 16.12affected · rpm
- 15 and later · before 15.16affected · rpm
- before 14.21affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | postgresql | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-contrib | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-docs | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-plperl | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-plpython3 | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-pltcl | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-private-devel | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-private-libs | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-server | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-server-devel | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-static | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-test | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-test-rpm-macros | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-upgrade | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql-upgrade-devel | before 16.13-1.el10_2 | 16.13-1.el10_2 |
| AlmaLinux:10 | postgresql18 | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-contrib | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-docs | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-plperl | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-plpython3 | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-devel | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-libs | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-server | before 18.3-1.el10_2 | 18.3-1.el10_2 |
| AlmaLinux:10 | postgresql18-server-devel | before 18.3-1.el10_2 | 18.3-1.el10_2 |
+96
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to 55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
- CVE-2007-3280The Database Link library (dblink) in PostgreSQL 8.1 implements functions via CREATE statements that map to arbitrary libraries based on the44Plan
- CVE-2013-1899Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows remote attackers to ca42Plan
- CVE-2018-16850postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ...41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a PostgreSQL | 14.21 | Vendor (CNA) |
| n/a PostgreSQL | 15.16 | Vendor (CNA) |
| n/a PostgreSQL | 16.12 | Vendor (CNA) |
| n/a PostgreSQL | 17.8 | Vendor (CNA) |
| n/a PostgreSQL | 18.2 | Vendor (CNA) |
| almalinux:postgresql18 | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-contrib | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-docs | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-plperl | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-plpython3 | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-private-devel | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-private-libs | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-server | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-server-devel | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-static | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-test | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-test-rpm-macros | 18.3-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:postgresql15 | 15.16-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:postgresql16 | 16.12-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:postgresql17 | 17.8-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql18 | 18.2-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:postgresql-15 | 15.16-0+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:postgresql-17 | 17.8-0+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:postgresql-18 | 18.2-1 · Debian:14 | Package registry (OSV) |
| opensuse:postgresql14 | 14.22-150600.16.28.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:postgresql15 | 15.17-150600.16.28.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:postgresql16 | 16.13-150600.16.30.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:postgresql17 | 17.9-150600.13.24.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:postgresql18 | 18.3-150600.13.8.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:postgresql18-mini | 18.3-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
+29
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-20040 days apartPostgreSQL intarray missing validation of type of input to selectivity estimator executes arbitrary code35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-1287 · Improper Validation of Specified Type of InputCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.