CVE-2026-14676: PostgreSQL pg_stat_statements heap buffer overflow executes arbitrary code
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
- 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 18.6.
Low priority for now. Upgrade to n/a PostgreSQL 18.6 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 pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.
- Published
- Aug 13, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.4% · 38th 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 · 0.4%
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
- No public exploit code on record
- 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.6affected · rpm
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql18.0 and later · before 18.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | postgresql18 | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-contrib | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-docs | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-plperl | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-plpython3 | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-devel | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-libs | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-server | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-server-devel | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-static | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-test | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-test-rpm-macros | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-upgrade | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:10 | postgresql18-upgrade-devel | before 18.6-1.el10_2 | 18.6-1.el10_2 |
| AlmaLinux:9 | pg_repack | before 1.5.3-1.module_el9.8.0+234+5456f35d | 1.5.3-1.module_el9.8.0+234+5456f35d |
| AlmaLinux:9 | pgaudit | before 18.0-1.module_el9.8.0+234+5456f35d | 18.0-1.module_el9.8.0+234+5456f35d |
| AlmaLinux:9 | pgvector | before 0.8.1-1.module_el9.8.0+234+5456f35d | 0.8.1-1.module_el9.8.0+234+5456f35d |
| AlmaLinux:9 | postgis | before 3.6.1-4.module_el9.8.0+310+22372bcc | 3.6.1-4.module_el9.8.0+310+22372bcc |
| AlmaLinux:9 | postgis-client | before 3.6.1-4.module_el9.8.0+310+22372bcc | 3.6.1-4.module_el9.8.0+310+22372bcc |
| AlmaLinux:9 | postgis-docs | before 3.6.1-4.module_el9.8.0+310+22372bcc | 3.6.1-4.module_el9.8.0+310+22372bcc |
| AlmaLinux:9 | postgis-upgrade | before 3.6.1-4.module_el9.8.0+310+22372bcc | 3.6.1-4.module_el9.8.0+310+22372bcc |
| AlmaLinux:9 | postgis-utils | before 3.6.1-4.module_el9.8.0+310+22372bcc | 3.6.1-4.module_el9.8.0+310+22372bcc |
| AlmaLinux:9 | postgres-decoderbufs | before 3.3.1-1.Final.module_el9.8.0+234+5456f35d | 3.3.1-1.Final.module_el9.8.0+234+5456f35d |
| AlmaLinux:9 | postgresql | before 18.6-1.module_el9.8.0+310+22372bcc | 18.6-1.module_el9.8.0+310+22372bcc |
+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-14672Aug 13, 2026 · PostgreSQL observable response discrepancy with non-default scram_iterations provides user existence oracle21Monitor
- ← EarlierCVE-2026-14673Aug 13, 2026 · PostgreSQL amcheck does not clear untrusted search path15Monitor
- Later →CVE-2026-14677Aug 13, 2026 · PostgreSQL 32-bit pltcl and plperl undersize allocations, via integer wraparound35Monitor
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 | 18.6 | Vendor (CNA) |
| almalinux:postgresql18 | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-contrib | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-docs | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-plperl | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-plpython3 | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-private-devel | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-private-libs | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-server | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-server-devel | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-static | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-test | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:postgresql18-test-rpm-macros | 18.6-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:postgresql15 | 15.19-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql16 | 16.15-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql17 | 17.11-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql18 | 18.5-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:postgresql-18 | 18.6-1 · Debian:14 | Package registry (OSV) |
| opensuse:postgresql18 | 18.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql18-mini | 18.6-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:postgresql18 | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-contrib | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-contrib-debuginfo | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-debuginfo | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-debugsource | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-docs | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-docs-debuginfo | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-plperl | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-plperl-debuginfo | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:postgresql18-plpython3 | 0:18.6-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+8
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).
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-146640 days apartPostgreSQL regexp heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-146690 days apartPostgreSQL to_char heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-146700 days apartPostgreSQL plperl tied object heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-193850 days apartPostgreSQL pg_dump heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-2005182 days apartPostgreSQL pgcrypto heap buffer overflow executes arbitrary code35Monitor
- CVE-2026-2007182 days apartPostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory32Monitor
Not on record for this CVE: 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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.