CVE-2026-6476 | PostgreSQL pg_createsubscriber allows SQL injection via subscription name

SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.

Published: 2026-05-14 Last update: 2026-05-18 Assigner: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-6476 is rated Low Risk (31.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-6476

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-15 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-6476

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 5.9 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Weakness enumeration for CVE-2026-6476

GitHub Security Advisory for CVE-2026-6476

GHSA-9crw-q654-rwgr · Severity: high — SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription...

OS Trackers for CVE-2026-6476

vendor priority summary link
debian not yet assigned CVE-2026-6476 not yet assigned priority: Debian including 2 source packages (postgresql-17, postgresql-18), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2026-6476
suse high CVE-2026-6476 severity important: SUSE including 98 source package names (libecpg6, libecpg6-17.10-3.27.1, …), 634 product×package rows across 31 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (31 product lines)): Known Not Affected 505, Fixed 125, First Fixed 4. https://www.suse.com/security/cve/CVE-2026-6476/
ubuntu medium CVE-2026-6476 medium priority: Ubuntu including 8 source packages (postgresql-10, postgresql-12, …), 44 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 28, needs-triage 7, ignored 4, released 4, deferred 1. https://ubuntu.com/security/CVE-2026-6476

Affected software / configurations for CVE-2026-6476

Vendor Product Version Raw CPE
postgresql postgresql >= 17.0, < 17.10 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 18.0, < 18.4 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*

References for CVE-2026-6476

cvelogic Threat Intelligence