Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-18024: Buffer Over-read in PostgreSQL

0
Medium
VulnerabilityCVE-2026-18024cvecve-2026-18024
Published: 08/13/2026 (08/13/2026, 13:00:14 UTC)
Source: CVE Database V5
Product: PostgreSQL

Description

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.

CVSS v3.1

Score 4.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected software

Postgresqlmore threats →ai
postgresql/postgresql
pkg:deb/postgresql/postgresql
Affected versions
<14.24<15.19<16.15<17.11<18.5

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/13/2026, 13:43:36 UTC

Technical Analysis

This vulnerability involves a buffer over-read in the ascii() function of PostgreSQL, which can disclose up to 3 bytes of memory beyond the intended allocation when processing a crafted input string. It affects PostgreSQL versions earlier than 14.24, 15.19, 16.15, 17.11, and 18.5. The flaw is a lesser-impact variant of a previously addressed issue (CVE-2026-2006). The vulnerability requires low privileges to exploit and does not impact integrity or availability, only confidentiality to a limited extent.

Potential Impact

An attacker with limited privileges can cause the ascii() function to read and disclose up to 3 bytes of memory beyond the allocated buffer. This could lead to minor information disclosure but does not affect data integrity or system availability. The impact is limited in scope and severity.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the current data. Users should monitor PostgreSQL vendor advisories for updates and apply patches once available.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
PostgreSQL
Date Reserved
2026-07-28T01:59:49.926Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a7dc619bf8831d5393e5400

Added to database: 08/13/2026, 13:26:49 UTC

Last enriched: 08/13/2026, 13:43:36 UTC

Last updated: 08/13/2026, 23:40:59 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses