CVE-2026-18024: PostgreSQL ascii() function reads past end of buffer
Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end of a specific allocation, via a crafted text value. This is the same class of defect that CVE-2026-2006 fixed, though this instance has less impact. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 18.5 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 17.11 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 16.15 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 15.19 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 14.24
Event History
Frequently Asked Questions
What is the severity of CVE-2026-18024?
The severity of CVE-2026-18024 is medium with a score of 4.3.
How does CVE-2026-18024 affect PostgreSQL?
CVE-2026-18024 allows a buffer over-read in the ascii() function, disclosing up to 3 bytes of data after the end of a specific allocation.
What versions of PostgreSQL are affected by CVE-2026-18024?
CVE-2026-18024 affects PostgreSQL versions prior to 18.5, 17.11, and 16.15.
How can I mitigate CVE-2026-18024 in my PostgreSQL installation?
To mitigate CVE-2026-18024, upgrade to PostgreSQL version 18.5, 17.11, or 16.15 or later.
Is there a workaround for CVE-2026-18024 until I can upgrade?
There are no specific workarounds for CVE-2026-18024; upgrading is recommended to eliminate the vulnerability.