CVE-2026-50738

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A use-after-free condition exists in pglogical's worker signaling code, where a worker structure can be dereferenced after the underlying slot has been freed or recycled during normal worker lifecycle events. The condition is reachable during normal replication operation, including by a low-privileged user able to influence worker start, stop, and restart timing through permitted pglogical operations. In the typical case the condition crashes replication workers, causing an availability impact. In the worst case a use-after-free in a PostgreSQL backend can be leveraged as a remote code execution primitive at the privilege of that backend.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.5% × 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.5%
EPSS %ILE
41st
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-50738(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 12× in last 7d / 58× 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 209 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 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50738?
CVE-2026-50738 is a medium-severity vulnerability; its CVE record was published on July 28, 2026. A use-after-free condition exists in pglogical's worker signaling code, where a worker structure can be dereferenced after the underlying slot has been freed or recycled during normal worker lifecycle events. The condition is reachable during normal replication operation, including by a…
When was the CVE record for CVE-2026-50738 published?
The CVE record for CVE-2026-50738 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-50738 actively exploited?
CVE-2026-50738 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50738?
CVE-2026-50738 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-50738?
A fix for CVE-2026-50738 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50738 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-50738

Explore →

Is Your Infrastructure Affected by CVE-2026-50738?

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

Book a Demo →Browse All CVEs