PostgreSQL ECPG · Integer Underflow
Source GCVE Database
Not known to be exploited · CVSS 3.8 Low · fixed in 18.6 : update PostgreSQL when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 18.6, 17.11, 16.15 +3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until patched, limit database server administrator privileges and avoid sending malformed bytea values to the ECPG client.
Description
An integer underflow vulnerability in PostgreSQL ECPG client allows a database server administrator to cause a temporary denial of service by sending a malformed bytea value without the required prefix. This leads to the client overwriting a large memory region, usually resulting in a segmentation fault. In rare cases, this may cause client-specific integrity issues. The vulnerability affects PostgreSQL versions prior to 18.5, 17.11, 16.15, 15.19, and 14.24.