CVE-2026-6476

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated May 18, 2026
No patch confirmed yet.
generic

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

https://www.postgresql.org/support/security/CVE-2026-6476/

Vendor Advisories for CVE-2026-6476(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-16 (16.14-0ubuntu0.24.04.1) @ noble2026-08-23ubuntu
redhatpostgresql18-0:18.4-1.el10_22026-06-22redhat
redhatpostgresql:18-9080020260605125734.rhel92026-06-16redhat
redhatpostgresql18-main-18.4-0.1.hum12026-06-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 6 ecosystems)
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.4-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.4-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.5-1 ... 17.9-0+deb13u1 (6 versions)17.10-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (19 versions)18.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 290 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-12 15:02 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-26 14:47 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 17:41 UTCEG score recompute
  22. 2026-08-23 17:41 UTCVendor advisory
  23. 2026-08-23 17:41 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 01:52 UTCEG score recompute
Show 75 more
  1. 2026-08-22 01:52 UTCVendor advisory
  2. 2026-08-22 01:52 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 19:40 UTCEG score recompute
  6. 2026-08-20 19:40 UTCVendor advisory
  7. 2026-08-20 19:40 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 10:26 UTCEG score recompute
  13. 2026-08-17 10:26 UTCVendor advisory
  14. 2026-08-17 10:26 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 03:58 UTCEG score recompute
  18. 2026-08-16 03:58 UTCVendor advisory
  19. 2026-08-16 03:58 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-15 00:22 UTCVendor advisory
  23. 2026-08-15 00:22 UTCGHSA enrichment
  24. 2026-08-14 13:24 UTCVendor advisory
  25. 2026-08-14 13:24 UTCGHSA enrichment
  26. 2026-08-14 02:26 UTCEG score recompute
  27. 2026-08-14 02:26 UTCVendor advisory
  28. 2026-08-14 02:26 UTCGHSA enrichment
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 01:59 UTCVendor advisory
  31. 2026-08-13 01:59 UTCGHSA enrichment
  32. 2026-08-12 15:01 UTCEG score recompute
  33. 2026-08-12 15:01 UTCVendor advisory
  34. 2026-08-12 15:01 UTCGHSA enrichment
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-11 15:26 UTCEG score recompute
  37. 2026-08-11 15:26 UTCVendor advisory
  38. 2026-08-11 15:26 UTCGHSA enrichment
  39. 2026-08-11 00:54 UTCEG score recompute
  40. 2026-08-11 00:54 UTCVendor advisory
  41. 2026-08-11 00:53 UTCGHSA enrichment
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 11:29 UTCVendor advisory
  44. 2026-08-10 11:29 UTCGHSA enrichment
  45. 2026-08-09 23:46 UTCEG score recompute
  46. 2026-08-09 23:46 UTCVendor advisory
  47. 2026-08-09 23:46 UTCGHSA enrichment
  48. 2026-08-09 13:47 UTCEPSS rescore
  49. 2026-08-09 12:49 UTCVendor advisory
  50. 2026-08-09 12:49 UTCGHSA enrichment
  51. 2026-08-09 01:51 UTCEG score recompute
  52. 2026-08-09 01:51 UTCVendor advisory
  53. 2026-08-09 01:51 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-08 04:33 UTCVendor advisory
  56. 2026-08-08 04:33 UTCGHSA enrichment
  57. 2026-08-07 17:35 UTCEG score recompute
  58. 2026-08-07 17:35 UTCVendor advisory
  59. 2026-08-07 17:35 UTCGHSA enrichment
  60. 2026-08-07 06:37 UTCVendor advisory
  61. 2026-08-07 06:37 UTCGHSA enrichment
  62. 2026-08-06 19:33 UTCEG score recompute
  63. 2026-08-06 19:33 UTCVendor advisory
  64. 2026-08-06 19:33 UTCGHSA enrichment
  65. 2026-08-06 13:47 UTCEPSS rescore
  66. 2026-08-06 08:35 UTCVendor advisory
  67. 2026-08-06 08:35 UTCGHSA enrichment
  68. 2026-08-05 21:37 UTCEG score recompute
  69. 2026-08-05 21:37 UTCVendor advisory
  70. 2026-08-05 21:37 UTCGHSA enrichment
  71. 2026-08-05 19:17 UTCEPSS rescore
  72. 2026-08-05 19:17 UTCEPSS rescore
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 10:39 UTCEPSS rescore
  75. 2026-08-04 05:59 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-6476?
CVE-2026-6476 is a high vulnerability published on May 14, 2026. SQL injection in PostgreSQL pgcreatesubscriber allows an attacker with pgcreatesubscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pgcreatesubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected.…
When was CVE-2026-6476 disclosed?
CVE-2026-6476 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6476 actively exploited?
CVE-2026-6476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-6476?
CVE-2026-6476 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-6476?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6476, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6476

Explore →

Is Your Infrastructure Affected by CVE-2026-6476?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs