Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-15742: PostgreSQL fuzzystrmatch writes effectively-arbitrary addresses, via integer wraparound

CVE-2026-15742 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
7.5 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · base score 8.8, scored by PostgreSQLAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-190 Integer Overflow or Wraparound
EPSS
0.60% chance of exploitation in the next 30 days (49th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
Fixed releases
  • Red Hat: postgresql18-0:18.6-1.el10_2, postgresql16-0:16.15-1.el10_2, postgresql16-0:16.15-1.el10_0, postgresql-0:9.2.24-9.el7_9.7, postgresql:16-8100020260910192321.489197e6, postgresql:15-8100020260906175012.489197e6 and 39 more in the advisory
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-15742; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). 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-15742?

Upgrade to a fixed release named by the vendor:

  • Red Hat: postgresql18-0:18.6-1.el10_2, postgresql16-0:16.15-1.el10_2, postgresql16-0:16.15-1.el10_0, postgresql-0:9.2.24-9.el7_9.7, postgresql:16-8100020260910192321.489197e6, postgresql:15-8100020260906175012.489197e6
  • To mitigate this issue, consider disabling the `fuzzystrmatch` extension within PostgreSQL if its functionality is not essential. Alternatively, the `postgresql-fuzzystrmatch` package can be removed. Disabling or removing the extension may affect applications that rely on the `levenshtein()` or `levenshtein_less_equal()` functions. A database service restart may be required for these changes to take effect. (Red Hat)

Vendor advisories for CVE-2026-15742

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-15742] PostgreSQL fuzzystrmatch: Arbitrary code execution via integer wraparound

    CVE-2026-15742Source published Source updated

    Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. This vulnerability in the PostgreSQL `fuzzystrmatch` extension is rated as Important. This risk is present only when the `fuzzystrmatch` extension is explicitly installed and utilized, as it is not enabled by default in Red Hat deployments. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-190.

    Affected products in this advisory
    • Red Hat Enterprise Linux 10.0 Extended Update Support
    • Red Hat Enterprise Linux 7 Extended Lifecycle Support
    • Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
    • Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

    12 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
    • postgresql18-0:18.6-1.el10_2
    • postgresql16-0:16.15-1.el10_2
    • postgresql16-0:16.15-1.el10_0
    • postgresql-0:9.2.24-9.el7_9.7

    41 more entries in the full advisory.

    Mitigation guidance
    • To mitigate this issue, consider disabling the `fuzzystrmatch` extension within PostgreSQL if its functionality is not essential. Alternatively, the `postgresql-fuzzystrmatch` package can be removed. Disabling or removing the extension may affect applications that rely on the `levenshtein()` or `levenshtein_less_equal()` functions. A database service restart may be required for these changes to take effect.

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. First vendor advisory listed by VulniPulse
  3. CVE record last updated

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