PostgreSQL ascii() SQL function · Buffer Over-read
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 4.3 Medium · 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 23% 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:L/UI:N/S:U/C:L/I:N/A:NExploitation 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
A fix is available in PostgreSQL versions 18.5, 17.11, 16.15, 15.19, and 14.24. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated.
Description
A buffer over-read vulnerability exists in the PostgreSQL ascii() SQL function that allows a user with limited privileges to read up to 3 bytes beyond the allocated memory of a crafted text value. This flaw affects PostgreSQL versions prior to 18.5, 17.11, 16.15, 15.19, and 14.24 and is similar to a previously fixed issue (CVE-2026-2006) but with less impact.