Skip to content
Noroxi
CVE-2026-6476· NVD / CVE Program· CNA PostgreSQL

PostgreSQL pg_createsubscriber allows SQL injection via subscription name

Noroxi assessment

Priority: Monitor (action score 28/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.28% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: n/a PostgreSQL 17.10, 18.4.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to n/a PostgreSQL 17.10, 18.4 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

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.

HighCVSS 7.2 · v3.1—No exploit Fix available
Published
May 14, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 20th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PostgreSQL
7.2
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.

Follow CVE-2026-6476

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
postgresqlpostgresql

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

Add to my stack

Affected versions

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

  • 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

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10postgresql18before 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-contribbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-docsbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-plperlbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-plpython3before 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-private-develbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-private-libsbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-serverbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-server-develbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-staticbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-testbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-test-rpm-macrosbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-upgradebefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:10postgresql18-upgrade-develbefore 18.6-1.el10_218.6-1.el10_2
AlmaLinux:9pg_repackbefore 1.5.3-1.module_el9.8.0+234+5456f35d1.5.3-1.module_el9.8.0+234+5456f35d
AlmaLinux:9pgauditbefore 18.0-1.module_el9.8.0+234+5456f35d18.0-1.module_el9.8.0+234+5456f35d
AlmaLinux:9pgvectorbefore 0.8.1-1.module_el9.8.0+234+5456f35d0.8.1-1.module_el9.8.0+234+5456f35d
AlmaLinux:9postgisbefore 3.6.1-4.module_el9.8.0+310+22372bcc3.6.1-4.module_el9.8.0+310+22372bcc
AlmaLinux:9postgis-clientbefore 3.6.1-4.module_el9.8.0+310+22372bcc3.6.1-4.module_el9.8.0+310+22372bcc
AlmaLinux:9postgis-docsbefore 3.6.1-4.module_el9.8.0+310+22372bcc3.6.1-4.module_el9.8.0+310+22372bcc
AlmaLinux:9postgis-upgradebefore 3.6.1-4.module_el9.8.0+310+22372bcc3.6.1-4.module_el9.8.0+310+22372bcc
AlmaLinux:9postgis-utilsbefore 3.6.1-4.module_el9.8.0+310+22372bcc3.6.1-4.module_el9.8.0+310+22372bcc
AlmaLinux:9postgres-decoderbufsbefore 3.3.1-1.Final.module_el9.8.0+234+5456f35d3.3.1-1.Final.module_el9.8.0+234+5456f35d
AlmaLinux:9postgresqlbefore 18.6-1.module_el9.8.0+310+22372bcc18.6-1.module_el9.8.0+310+22372bcc

+96

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 / packageFixed versionSource
n/a PostgreSQL17.10Vendor (CNA)
n/a PostgreSQL18.4Vendor (CNA)
almalinux:postgresql1818.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-contrib18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-docs18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-plperl18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-plpython318.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-private-devel18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-private-libs18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-server18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-server-devel18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-static18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-test18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:postgresql18-test-rpm-macros18.6-1.el10_2 · AlmaLinux:10Package registry (OSV)
alpine:postgresql1717.10-r0 · Alpine:v3.21Package registry (OSV)
alpine:postgresql1818.4-r0 · Alpine:v3.23Package registry (OSV)
debian:postgresql-1717.10-0+deb13u1 · Debian:13Package registry (OSV)
debian:postgresql-1818.4-1 · Debian:14Package registry (OSV)
opensuse:postgresql1717.10-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1818.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:pg_repack0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pg_repack-debuginfo0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pg_repack-debugsource0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgaudit0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgaudit-debuginfo0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgaudit-debugsource0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgvector0:0.8.1-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgvector-debuginfo0:0.8.1-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:pgvector-debugsource0:0.8.1-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:postgresql0:18.4-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+19

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.

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

Variant candidates

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

  • CVE-2026-66370 days apartPostgreSQL refint allows stack buffer overflow and SQL injection
    35Monitor
  • CVE-2026-66380 days apartPostgreSQL REFRESH PUBLICATION allows SQL injection via table name
    35Monitor
  • CVE-2026-1574191 days apartPostgreSQL expression deparse allows SQL injection via EXTRACT argument
    35Monitor

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.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Change log

  1. Fix✗ → ✓

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

References

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

All records