Read the docs

PostgreSQL REASSIGN OWNED bypasses role SET and CREATEDB checks

Priority LOW 20CWE-862Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
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. Impact type from CWE-862.

Summary

PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, and 14.25 are affected by missing authorization (CWE-862) in REASSIGN OWNED, which lets a role that has INHERIT but not SET transfer objects to the granted role. The same flaw allows reassigning database ownership without the CREATEDB privilege, which the equivalent ALTER ... OWNER commands block. A low-privileged authenticated user can exploit this over the network.

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

Description from the CNA

Missing authorization in PostgreSQL REASSIGN OWNED allows a role granted INHERIT but not SET to transfer objects to the granted role. It also allows reassignment of database ownership without the CREATEDB privilege. The equivalent ALTER ... OWNER commands block this. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Why it matters now

EPSS 0.00254 17th 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

Not available: CISA has not published SSVC decision points for this record.

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 fixes Red Hat Hardened Images in RHSA-2026:99821. Red Hat lists no plan for Red Hat Hardened Images without a fix.

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

  • 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: Moderate. 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-120146
  2. 2026-11-12 Alias added: GHSA-v5xq-4x8p-53j2
  3. 2026-11-12 Affected versions changed · Red Hat
  4. 2026-11-12 CVSS score added · Red Hat
  5. 2026-11-13 Fix available: RHSA-2026:99821 · Red Hat
  6. 2026-11-14 Fix available: Red Hat Hardened Images · Red Hat

References

Sources