Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-6470: PostgreSQL fails to check type USAGE privilege

CVE-2026-6470 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:N/I:N/A:L · base score 4.3, scored by PostgreSQLAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: low.
Weakness
  • CWE-862 Missing Authorization
EPSS
0.33% chance of exploitation in the next 30 days (26th 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-6470; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. 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-6470?

  • To mitigate this vulnerability, administrators can proactively monitor for and manually remove unauthorized dependencies created on composite types by users lacking USAGE privileges. Restricting database access and object creation rights only to trusted users will limit the exposure. (Red Hat)

Vendor advisories for CVE-2026-6470

Red Hat

1 advisory
  • Advisory severityMedium4.3

    Medium [CVE-2026-6470] Denial of Service via missing authorization in DDL commands

    CVE-2026-6470Source published Source updated

    Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. A flaw was found in PostgreSQL where missing authorization checks in DDL commands allow an authenticated user to create unauthorized dependencies on a data type (such as when assigning a range subtype or referencing the type in an SQL expression). This allows the user to block legitimate owners from altering or dropping that type, resulting in a targeted denial-of-service condition on the affected database…

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

    3 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 vulnerability, administrators can proactively monitor for and manually remove unauthorized dependencies created on composite types by users lacking USAGE privileges. Restricting database access and object creation rights only to trusted users will limit the exposure.

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