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.5, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-16241
Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-08-13. a secondary CVSS source baseline 3.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.8
- EG Score
- 3.8(high)
- EG Risk
- 17(Track)EG Risk 17/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity38% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 19, 2026
References (1)
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007https://www.postgresql.org/support/security/CVE-2026-16241/
Vendor Advisories for CVE-2026-16241(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 15:04 UTCGHSA enrichment
- 2026-08-18 15:33 UTCEG score recompute
- 2026-08-18 15:33 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:55 UTCEG score recompute
- 2026-08-16 20:55 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 16:29 UTCEG score recompute
- 2026-08-13 16:29 UTCGHSA enrichment
- 2026-08-13 16:01 UTCEG score recompute
- 2026-08-13 16:01 UTCGHSA enrichment
- 2026-08-13 13:35 UTCEG score recompute
- 2026-08-13 13:17 UTCEG score recompute
- 2026-08-13 13:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-191
Frequently asked(5)
What is CVE-2026-16241?
When was CVE-2026-16241 disclosed?
Is CVE-2026-16241 actively exploited?
What is the CVSS score of CVE-2026-16241?
How do I remediate CVE-2026-16241?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16241
Is Your Infrastructure Affected by CVE-2026-16241?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.