CVE-2026-50736

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-28. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The pglogical queue mechanism, used to convey out-of-band commands such as replicated DDL from a publisher to a subscriber, executes message payloads on the subscriber at the privilege level of the apply worker, which is equivalent to a PostgreSQL superuser in default installations. A party acting as the publisher can send crafted queue messages that cause arbitrary SQL to be executed on the subscriber as superuser, escalating from a role permitted to use pglogical to full superuser and breaking the isolation between tenants in shared deployments. To exploit the issue an attacker must be able to direct a subscription at an endpoint they control. In default installations this requires privileges normally reserved for a superuser, so the issue is most relevant to managed deployments where the ability to create subscriptions has been delegated to non-superuser roles.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 28, 2026

Last Modified

August 24, 2026

References (1)

Vendor Advisories for CVE-2026-50736(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pglogical2.3.3-3 ... 2.4.8-1 (19 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pglogical2.4.2-3 ... 2.4.8-1 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pglogical2.4.5-1, 2.4.6-1, 2.4.6-2, 2.4.7-1, 2.4.8-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pglogical2.4.5-1, 2.4.6-1, 2.4.6-2, 2.4.7-1
  • every version up to 2.4.8-1: fixed in 2.4.8-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 327 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 227 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50736?
CVE-2026-50736 is a high-severity vulnerability; its CVE record was published on July 28, 2026. The pglogical queue mechanism, used to convey out-of-band commands such as replicated DDL from a publisher to a subscriber, executes message payloads on the subscriber at the privilege level of the apply worker, which is equivalent to a PostgreSQL superuser in default installations. A party acting…
When was the CVE record for CVE-2026-50736 published?
The CVE record for CVE-2026-50736 was published on July 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 24, 2026; the record at its source may have been updated since.
Is CVE-2026-50736 actively exploited?
CVE-2026-50736 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50736?
CVE-2026-50736 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50736?
A fix for CVE-2026-50736 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50736 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50736?

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

Book a Demo →Browse All CVEs