CVE-2026-2005: PostgreSQL pgcrypto heap buffer overflow executes arbitrary code
Noroxi assessment
Priority: Monitor (action score 35/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.9% of all records.
- 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.
- Fixed version: n/a PostgreSQL 14.21, 15.16, 16.12.
Low priority for now. Upgrade to n/a PostgreSQL 14.21, 15.16, 16.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
- BDU:2026-01722
- ALSA-2026:19009
- ALSA-2026:19010
- ALSA-2026:3730
- ALSA-2026:3887
- ALSA-2026:3896
- ALSA-2026:4024
- ALSA-2026:4059
- ALSA-2026:4063
- ALSA-2026:4064
- ALSA-2026:4110
- 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
- Published
- Feb 12, 2026
- Updated
- Jul 15, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-122
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 8.8
- 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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is PostgreSQL on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions 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
Affected versions · NVD (5)
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
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-test-rpm-macros | before 16.13-1.el10_1 | 16.13-1.el10_1 |
| 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 |
+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…57Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2026-2003Feb 12, 2026 · PostgreSQL oidvector discloses a few bytes of memory17Monitor
- ← EarlierCVE-2026-2004Feb 12, 2026 · PostgreSQL intarray missing validation of type of input to selectivity estimator executes arbitrary code35Monitor
- Later →CVE-2026-2006Feb 12, 2026 · PostgreSQL missing validation of multibyte character length executes arbitrary code35Monitor
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) |
+30
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×5
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 5 repositories | 2026-03-07 → 2026-08-10 |
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.
- Published
- First PoC+23 d
- TodayNov 16, 2026+277 d
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-14664182 days apartPostgreSQL regexp heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-14669182 days apartPostgreSQL to_char heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-14670182 days apartPostgreSQL plperl tied object heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-14676182 days apartPostgreSQL pg_stat_statements heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-19385182 days apartPostgreSQL pg_dump heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-20070 days apartPostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory32Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:19009
- access.redhat.com/errata/RHSA-2026:19010
- access.redhat.com/errata/RHSA-2026:3730
- access.redhat.com/errata/RHSA-2026:3887
- access.redhat.com/errata/RHSA-2026:3896
- access.redhat.com/errata/RHSA-2026:4024
- access.redhat.com/errata/RHSA-2026:4059
- access.redhat.com/errata/RHSA-2026:4063
- access.redhat.com/errata/RHSA-2026:4064
- access.redhat.com/errata/RHSA-2026:4074
- access.redhat.com/errata/RHSA-2026:4075
- access.redhat.com/errata/RHSA-2026:4110
- access.redhat.com/errata/RHSA-2026:4254
- access.redhat.com/errata/RHSA-2026:4441
- access.redhat.com/errata/RHSA-2026:4475
- access.redhat.com/errata/RHSA-2026:4504
- access.redhat.com/errata/RHSA-2026:4505
- access.redhat.com/errata/RHSA-2026:4506
- access.redhat.com/errata/RHSA-2026:4509
Vendor advisories and official records. Exploit/PoC links are deliberately left out.