Read the docs

PostgreSQL type creation in pg_temp lets attackers run SQL as callers

Priority MEDIUM 41CWE-424Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 1 fixed, 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.

Summary

PostgreSQL versions before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected. Security-restricted operations can create domain, enum, or range types in pg_temp, an alternate path that CWE-424 covers. An object creator with low privileges can run arbitrary SQL as the operation's caller once a victim session later runs a query with an unqualified type name. Autovacuum and other common security-restricted operation users are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Improper protection of alternate path in PostgreSQL security-restricted operations allows an object creator to execute arbitrary SQL as the operation's caller, via a domain, enum, or range type created in pg_temp. The victim session must later run a query containing an unqualified type name, e.g. "SELECT '1'::bigint"; autovacuum and other common security-restricted operation users do not do so, so they are unaffected. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00479 41st percentileScored 2026-11-16
Fix Partial PostgreSQL: 18.7, 17.12, 16.16 +2Red Hat: 1 advisoryRed Hat: 1 fixed, 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
—PostgreSQL18 to before 18.7; 17 to before 17.12; 16 to before 16.16; 15 to before 15.20; before 14.2518.7, 17.12, 16.16, 15.20, 14.25Patch availableCNA
  • PostgreSQL Vendor— Affected 18 to before 18.7; 17 to before 17.12; 16 to before 16.16; 15 to before 15.20; before 14.25 Fixed in 18.7, 17.12, 16.16, 15.20, 14.25 Patch available CNA

Remediation

Upgrade PostgreSQL to 18.7, 17.12, 16.16, 15.20 or 14.25. Red Hat advisory RHSA-2026:99821 covers Red Hat Hardened Images, and Red Hat lists no available fix plan for that product.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA PostgreSQL Fixed in 18.7, 17.12, 16.16, 15.20, 14.25

Red Hat 1 advisory

  • RHSA-2026:99821 Released 2026-11-12 · Red Hat rating Important
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images libpq-18.7-0.1.hum1@aarch64, libpq-18.7-0.1.hum1@s390x, libpq-18.7-0.1.hum1@src +4

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    PostgreSQL 14.25, 15.20 and 3 more versions

    40 records Highest priority Priority MEDIUM 27 MEDIUM, 13 LOW

    Other records, highest priority first

    • TI-2026-90384 Type confusion in PostgreSQL plpgsql allows arbitrary code executionPriority MEDIUM 41
    • TI-2026-90383 PostgreSQL domain check use-after-free allows code executionPriority MEDIUM 41
    • TI-2026-90382 Heap overflow in PostgreSQL foreign batch inserts allows code executionPriority MEDIUM 41

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Hardened ImagesAffectedNo fix yet
Red Hat Hardened ImagesFixed RHSA-2026:99821

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-116316
  2. 2026-11-12 Alias added: GHSA-vhhp-qrj9-rf8m
  3. 2026-11-12 Affected versions changed · Red Hat
  4. 2026-11-12 CVSS score added · Red Hat
  5. 2026-11-12 CISA SSVC decision points changed
  6. 2026-11-13 CISA SSVC decision points changed
  7. 2026-11-13 Fix available: Red Hat Hardened Images · Red Hat
  8. 2026-11-13 Fix available: RHSA-2026:99821 · Red Hat

References

Sources