High Injection

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 May 14, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: PostgreSQL

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.3% (30-day exploitation probability)+3
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.29%

ahead of 20% of scored CVEs · Oct 14, 2026

Affects

Postgresql

CVSS base

7.2

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — www.postgresql.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Postgresql Postgresql).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Postgresql	Postgresql	≥ 17.0 and < 17.10≥ 18.0 and < 18.4	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.2	CVSS 3.1	High	1.2	5.9	f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database
7.2	CVSS 3.1	High	—	—	PostgreSQL via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-89 · SQL Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 7.2
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
May 14, 2026 · PostgreSQL

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

www.postgresql.org/support/security/CVE-2026-6476/
Patch, Vendor Advisory, NIST National Vulnerability Database

Elsewhere on this site

Postgresql
every CVE for this vendor

Injection
same class

CWE-89
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-6471 Missing Authorization in Postgresql Aug 13, 2026
High CVE-2026-6464 Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to… Aug 13, 2026
Low CVE-2026-6469 Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns… Aug 13, 2026
Medium CVE-2026-6470 Missing Authorization in Postgresql Aug 13, 2026
High CVE-2026-19385 Heap-based Buffer Overflow in Postgresql Aug 13, 2026
High CVE-2026-18408 Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the… Aug 13, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-6476 is "PostgreSQL pg_createsubscriber allows SQL injection via subscription name", rated High. It affects Postgresql (Postgresql); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.