CVE-2026-6472· NVD / CVE Program· CNA PostgreSQL

PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: n/a PostgreSQL 14.23, 15.18, 16.14.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to n/a PostgreSQL 14.23, 15.18, 16.14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

MediumCVSS 5.4 · v3.1—No exploit Fix available

Published: May 14, 2026
Updated: Jun 17, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-862

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · PostgreSQL: 5.4; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
postgresql	postgresql	cpe:2.3:a:postgresql:postgresql

Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

postgresql postgresqlbefore 14.23
postgresql postgresql15.0 and later · before 15.18
postgresql postgresql16.0 and later · before 16.14
postgresql postgresql17.0 and later · before 17.10
postgresql postgresql18.0 and later · before 18.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.

n/a PostgreSQL
- 18 and later · before 18.4affected · rpm
- 17 and later · before 17.10affected · rpm
- 16 and later · before 16.14affected · rpm
- 15 and later · before 15.18affected · rpm
- before 14.23affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.20	postgresql15	before 15.18-r0	15.18-r0
Alpine:v3.20	postgresql16	before 16.14-r0	16.14-r0
Alpine:v3.21	postgresql17	before 17.10-r0	17.10-r0
Alpine:v3.23	postgresql18	before 18.4-r0	18.4-r0
Debian:12	postgresql-15	before 15.18-0+deb12u1	15.18-0+deb12u1
Debian:13	postgresql-17	before 17.10-0+deb13u1	17.10-0+deb13u1
Debian:14	postgresql-18	before 18.4-1	18.4-1
openSUSE:Leap 16.0	postgresql14	before 14.23-160000.1.1	14.23-160000.1.1
openSUSE:Leap 16.0	postgresql15	before 15.18-160000.1.1	15.18-160000.1.1
openSUSE:Leap 16.0	postgresql16	before 16.14-160000.1.1	16.14-160000.1.1
openSUSE:Leap 16.0	postgresql17	before 17.10-160000.1.1	17.10-160000.1.1
openSUSE:Tumbleweed	postgresql14	before 14.23-1.1	14.23-1.1
openSUSE:Tumbleweed	postgresql15	before 15.18-1.1	15.18-1.1
openSUSE:Tumbleweed	postgresql16	before 16.14-1.1	16.14-1.1
openSUSE:Tumbleweed	postgresql17	before 17.10-1.1	17.10-1.1
openSUSE:Tumbleweed	postgresql18	before 18.4-1.1	18.4-1.1
Red Hat:enterprise_linux_eus:10.0	postgresql	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-contrib	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-contrib-debuginfo	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-debuginfo	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-docs	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-docs-debuginfo	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-plperl	before 0:16.14-1.el10_0	0:16.14-1.el10_0
Red Hat:enterprise_linux_eus:10.0	postgresql-plperl-debuginfo	before 0:16.14-1.el10_0	0:16.14-1.el10_0

+96

Same product

postgresql: all records

Other highest-scoring records for the same primary product.

CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers
57Plan
CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to
55Plan
CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.
49Plan
CVE-2007-3280The Database Link library (dblink) in PostgreSQL 8.1 implements functions via CREATE statements that map to arbitrary libraries based on the
44Plan
CVE-2013-1899Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows remote attackers to ca
42Plan
CVE-2018-16850postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ...
41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
n/a PostgreSQL	14.23	Vendor (CNA)
n/a PostgreSQL	15.18	Vendor (CNA)
n/a PostgreSQL	16.14	Vendor (CNA)
n/a PostgreSQL	17.10	Vendor (CNA)
n/a PostgreSQL	18.4	Vendor (CNA)
alpine:postgresql15	15.18-r0 · Alpine:v3.20	Package registry (OSV)
alpine:postgresql16	16.14-r0 · Alpine:v3.20	Package registry (OSV)
alpine:postgresql17	17.10-r0 · Alpine:v3.21	Package registry (OSV)
alpine:postgresql18	18.4-r0 · Alpine:v3.23	Package registry (OSV)
debian:postgresql-15	15.18-0+deb12u1 · Debian:12	Package registry (OSV)
debian:postgresql-17	17.10-0+deb13u1 · Debian:13	Package registry (OSV)
debian:postgresql-18	18.4-1 · Debian:14	Package registry (OSV)
opensuse:postgresql14	14.23-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:postgresql15	15.18-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:postgresql16	16.14-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:postgresql17	17.10-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:postgresql18	18.4-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:pg_repack	0:1.4.8-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:pg_repack-debuginfo	0:1.4.8-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:pg_repack-debugsource	0:1.4.8-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:pgaudit	0:1.7.0-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:pgaudit-debuginfo	0:1.7.0-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:pgaudit-debugsource	0:1.7.0-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:postgres-decoderbufs	0:1.9.7-1.Final.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:postgresql	0:18.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:postgresql-test-rpm-macros	0:18.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:postgresql17	0:17.10-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:postgresql17-contrib	0:17.10-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:postgresql17-docs	0:17.10-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:postgresql17-plperl	0:17.10-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)

+15

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Jelte Fennema-Nio

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-647191 days apartPostgreSQL logical decoding can dlopen arbitrary file
28Monitor
CVE-2026-647091 days apartPostgreSQL fails to check type USAGE privilege
17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0254 · May 15, 2026(PostgreSQL Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

Exploitation of Thunderbolt Protection FlawsCAPEC-665likelihood: Low · Very High

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.postgresql.org/support/security/CVE-2026-6472/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records