Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-18024: PostgreSQL ascii() function reads past end of buffer

CVE-2026-18024 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
4.3 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N · base score 4.3, scored by PostgreSQLAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-126 Buffer Over-read
EPSS
0.30% chance of exploitation in the next 30 days (23rd percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Vendor advisories
2 from Red Hat, Splunk
Assigned by
PostgreSQL (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-18024; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Text from the CVE.org record (PostgreSQL).

How do I fix CVE-2026-18024?

  • To mitigate this allow only trusted roles to run arbitrary SQL, and do not let untrusted users call ascii() on values they supply. Use a UTF-8 database encoding so the server rejects invalid multibyte input at the protocol boundary where possible, and restrict database network access to trusted clients. (Red Hat)

Vendor advisories for CVE-2026-18024

Red Hat

1 advisory
  • Advisory severityMedium4.3

    Medium [CVE-2026-18024] Information disclosure via buffer over-read in ascii function

    CVE-2026-18024Source published Source updated

    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. A flaw was found in PostgreSQL. This could lead to limited information disclosure. This Moderate impact information disclosure flaw in PostgreSQL's `ascii()` SQL function allows an authenticated attacker to read up to 3 bytes of memory beyond an allocated buffer by providing a specially crafted text value. The limited scope of data disclosure contributes to its Moderate severity. Red Hat severity: Moderate — CVSS 4.3…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 6
    • Red Hat Enterprise Linux 7
    • Red Hat Enterprise Linux 8

    4 more entries in the full advisory.

    Source-reported affected versions
    • < 18.5
    • < 17.11
    • < 16.15
    • < 15.19

    1 more entries in the full advisory.

    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    • To mitigate this allow only trusted roles to run arbitrary SQL, and do not let untrusted users call ascii() on values they supply. Use a UTF-8 database encoding so the server rejects invalid multibyte input at the protocol boundary where possible, and restrict database network access to trusted clients.

Splunk

1 advisory
  • Advisory severityCritical

    Critical [CVE-2025-61726 +79] Third-Party Package Updates in Splunk Enterprise - November 2026

    SVD-2026-1104Source published

    This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Splunk remedied common vulnerabilities and exposures (CVEs) in third-party packages in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher. Affected products named by the advisory: Splunk Enterprise 10.6; Splunk Enterprise 10.4; Splunk Enterprise 10.2; Splunk Enterprise 10.0; and 1 more. Affected products named by the advisory: Splunk Enterprise 9.4.

    Affected products in this advisory
    • Splunk Enterprise 10.6
    • Splunk Enterprise 10.4
    • Splunk Enterprise 10.2
    • Splunk Enterprise 10.0

    1 more entries in the full advisory.

    Source-reported affected versions
    • Splunk Enterprise 10.6.0.5
    • Splunk Enterprise 10.4.0 to 10.4.4
    • Splunk Enterprise 10.2.0 to 10.2.8
    • Splunk Enterprise 10.0.0 to 10.0.11

    1 more entries in the full advisory.

    Source-reported fixed versions
    • Splunk Enterprise 10.6.1
    • Splunk Enterprise 10.4.5
    • Splunk Enterprise 10.2.9
    • Splunk Enterprise 10.0.12

    1 more entries in the full advisory.

    Mitigation guidance
    • Upgrade Splunk Enterprise to an applicable fixed release identified in the OSS entries below. The listed versions contain different component updates; the details specify which releases contain each fix.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All Red Hat advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat