cve.bz

CVE-2026-6467 PostgreSQL extension script schema mishandling executes arbitrary SQL

7.2 highEPSS 0.6%

High (7.2). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Uncontrolled search path element in PostgreSQL CREATE EXTENSION allows an attacker with database-level CREATE privilege to execute arbitrary code as the bootstrap superuser, via ALTER SCHEMA ... RENAME or CREATE EXTENSION ... SCHEMA "$user". ALTER EXTENSION was also affected. A trusted-extension script located the wrong object and executed arbitrary SQL of the attacker's choice. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-427 Uncontrolled Search Path Element
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
Assigned by
PostgreSQL (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-6467 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6467?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6467?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6467 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-6467

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-6467](https://cve.bz/cve/badge/CVE-2026-6467.svg)](https://cve.bz/cve/CVE-2026-6467)

HTML:

<a href="https://cve.bz/cve/CVE-2026-6467"><img src="https://cve.bz/cve/badge/CVE-2026-6467.svg" alt="CVE-2026-6467"></a>

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12postgresql-15no fix listedDEBIAN-CVE-2026-6467
Debian13postgresql-1717.12-0+deb13u1DEBIAN-CVE-2026-6467
Debian14postgresql-18no fix listedDEBIAN-CVE-2026-6467
Ubuntu20.04:LTSpostgresql-12no fix listedUBUNTU-CVE-2026-6467
Ubuntu22.04:LTSpostgresql-14no fix listedUBUNTU-CVE-2026-6467
Ubuntu24.04:LTSpostgresql-16no fix listedUBUNTU-CVE-2026-6467
Ubuntu26.04:LTS, 26.10postgresql-18no fix listedUBUNTU-CVE-2026-6467
UbuntuPro:14.04:LTSpostgresql-9.3no fix listedUBUNTU-CVE-2026-6467
UbuntuPro:16.04:LTSpostgresql-9.5no fix listedUBUNTU-CVE-2026-6467
UbuntuPro:18.04:LTSpostgresql-10no fix listedUBUNTU-CVE-2026-6467
Red Hathummingbird:1libpq, libpq-devel0:18.7-0.1.hum1RHSA-2026:99821
Alpinev3.21, v3.22postgresql1515.20-r0ALPINE-CVE-2026-6467
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1616.16-r0ALPINE-CVE-2026-6467
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1717.12-r0ALPINE-CVE-2026-6467
Alpinev3.23, v3.24postgresql1818.7-r0ALPINE-CVE-2026-6467
Azure Linux3postgresqlno fix listedAZL-113804

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important impact because an authenticated user possessing database creation rights can escalate privileges to the database bootstrap superuser, resulting in complete administrative control over the PostgreSQL instance. While the flaw demands pre-existing database credentials with database-level CREATE permissions, the resulting blast radius encompasses full compromise of database confidentiality, integrity, and availability. In standard Red Hat Enterprise Linux deployments, unprivileged users do not receive database-level CREATE permissions by default, limiting exposure to systems configured for non-superuser extension administration or delegated multi-tenant operations.

Red Hat's mitigation

Revoke database-level CREATE privileges from untrusted roles and restrict network access to the PostgreSQL service.

To prevent non-superusers from creating schemas or installing extensions, revoke the database creation privilege in PostgreSQL:

REVOKE CREATE ON DATABASE <database_name> FROM PUBLIC;

REVOKE CREATE ON DATABASE <database_name> FROM <role_name>;

Additionally, limit network exposure by restricting connections in pg_hba.conf to trusted hosts, or enforce firewall rules via firewalld:

firewall-cmd --permanent --zone=public --remove-service=postgresql

firewall-cmd --reload

If modifying pg_hba.conf, apply configuration changes using:

systemctl reload postgresql

Warning: Reloading the service or applying firewall rules will alter network connectivity and may disconnect clients that are not explicitly permitted. Revoking the CREATE privilege prevents affected accounts from defining new schemas or managing extensions until granted by a superuser.

ProductPackageStateAdvisory
Red Hat Hardened ImageslibpqAffected
Red Hat Hardened Imagespostgresql17Affected
Red Hat Hardened Imagespostgresql18Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-6467.

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
  • CAPEC-471 Search Order Hijacking Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON