CVE-2026-16241: PostgreSQL ECPG integer underflow can crash the client
Noroxi assessment
Priority: Monitor (action score 15/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.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a PostgreSQL 14.24, 15.19, 16.15.
Low priority for now. Upgrade to n/a PostgreSQL 14.24, 15.19, 16.15 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
Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix. The client overwrites a huge memory region with bytes outside attacker knowledge or control. This typically yields a simple SIGSEGV, but rare cases might achieve client-specific integrity impact via the write. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
- BDU:2026-11970
- EUVD-2026-57850
- openSUSE-SU-2026:11552-1
- openSUSE-SU-2026:11553-1
- openSUSE-SU-2026:11554-1
- openSUSE-SU-2026:11555-1
- openSUSE-SU-2026:21699-1
- openSUSE-SU-2026:21700-1
- openSUSE-SU-2026:21701-1
- openSUSE-SU-2026:21702-1
- SUSE-SU-2026:23578-1
- SUSE-SU-2026:23579-1
- SUSE-SU-2026:23580-1
- SUSE-SU-2026:23582-1
- SUSE-SU-2026:3793-1
- SUSE-SU-2026:3794-1
- SUSE-SU-2026:3940-1
- SUSE-SU-2026:3941-1
- SUSE-SU-2026:3943-1
- SUSE-SU-2026:3944-1
- Published
- Aug 13, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-191
Report tools
Action score
15
Monitor
Low priority for now.
- CVSS
- 15 / 40 · 3.8 / 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
- 3.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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 scanAffected 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.24
- postgresql postgresql15.0 and later · before 15.19
- postgresql postgresql16.0 and later · before 16.15
- postgresql postgresql17.0 and later · before 17.11
- postgresql postgresql18.0 and later · before 18.5
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.6affected · rpm
- 17 and later · before 17.11affected · rpm
- 16 and later · before 16.15affected · rpm
- 15 and later · before 15.19affected · rpm
- before 14.24affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | postgresql15 | before 15.19-r0 | 15.19-r0 |
| Alpine:v3.21 | postgresql16 | before 16.15-r0 | 16.15-r0 |
| Alpine:v3.21 | postgresql17 | before 17.11-r0 | 17.11-r0 |
| Alpine:v3.23 | postgresql18 | before 18.5-r0 | 18.5-r0 |
| Debian:12 | postgresql-15 | before 15.19-0+deb12u1 | 15.19-0+deb12u1 |
| Debian:13 | postgresql-17 | before 17.11-0+deb13u1 | 17.11-0+deb13u1 |
| Debian:14 | postgresql-18 | before 18.6-1 | 18.6-1 |
| openSUSE:Leap 16.0 | postgresql14 | before 14.24-160000.1.1 | 14.24-160000.1.1 |
| openSUSE:Leap 16.0 | postgresql15 | before 15.19-160000.1.1 | 15.19-160000.1.1 |
| openSUSE:Leap 16.0 | postgresql16 | before 16.15-160000.1.1 | 16.15-160000.1.1 |
| openSUSE:Leap 16.0 | postgresql17 | before 17.11-160000.1.1 | 17.11-160000.1.1 |
| openSUSE:Tumbleweed | postgresql14 | before 14.24-1.1 | 14.24-1.1 |
| openSUSE:Tumbleweed | postgresql15 | before 15.19-1.1 | 15.19-1.1 |
| openSUSE:Tumbleweed | postgresql16 | before 16.15-1.1 | 16.15-1.1 |
| openSUSE:Tumbleweed | postgresql17 | before 17.11-1.1 | 17.11-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | postgresql14 | before 14.24-150200.5.77.1 | 14.24-150200.5.77.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | postgresql15 | before 15.19-150200.5.62.1 | 15.19-150200.5.62.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | postgresql16 | before 16.15-150200.5.49.1 | 16.15-150200.5.49.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | postgresql17 | before 17.11-150200.5.33.1 | 17.11-150200.5.33.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | postgresql17 | before 17.11-150600.13.32.1 | 17.11-150600.13.32.1 |
| SUSE:Linux Enterprise Module for Legacy 15 SP7 | postgresql14 | before 14.24-150600.16.36.1 | 14.24-150600.16.36.1 |
| SUSE:Linux Enterprise Module for Legacy 15 SP7 | postgresql15 | before 15.19-150600.16.36.1 | 15.19-150600.16.36.1 |
| SUSE:Linux Enterprise Module for Legacy 15 SP7 | postgresql16 | before 16.15-150600.16.38.1 | 16.15-150600.16.38.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | postgresql14 | before 14.24-3.75.1 | 14.24-3.75.1 |
+6
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
Published before and after this one in the same product
- ← EarlierCVE-2026-16238Aug 13, 2026 · PostgreSQL type confusion in pg_restore_attribute_stats() executes arbitrary code35Monitor
- ← EarlierCVE-2026-16239Aug 13, 2026 · PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code35Monitor
- Later →CVE-2026-18024Aug 13, 2026 · PostgreSQL ascii() function reads past end of buffer17Monitor
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.24 | Vendor (CNA) |
| n/a PostgreSQL | 15.19 | Vendor (CNA) |
| n/a PostgreSQL | 16.15 | Vendor (CNA) |
| n/a PostgreSQL | 17.11 | Vendor (CNA) |
| n/a PostgreSQL | 18.6 | Vendor (CNA) |
| 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-15 | 15.19-0+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:postgresql-17 | 17.11-0+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:postgresql-18 | 18.6-1 · Debian:14 | Package registry (OSV) |
| opensuse:postgresql14 | 14.24-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql15 | 15.19-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql16 | 16.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql17 | 17.11-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:postgresql14 | 14.24-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:postgresql15 | 15.19-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:postgresql16 | 16.15-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:postgresql17 | 17.11-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
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.
No nightly-computed relations.
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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-191 · Integer Underflow (Wrap or Wraparound)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L
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.
Change 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.