CVE-2026-50735

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-07-28. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker. 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
6.8
EG Score
6.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 24, 2026

References (1)

Vendor Advisories for CVE-2026-50735(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 rangeFixed inDependents
pglogical2.3.3-3 ... 2.4.8-1 (19 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pglogical2.4.2-3 ... 2.4.8-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pglogical2.4.5-1, 2.4.6-1, 2.4.6-2, 2.4.7-1, 2.4.8-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pglogical2.4.5-1, 2.4.6-1, 2.4.6-2, 2.4.7-12.4.8-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 79× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:31 UTCEG score recompute
  3. 2026-08-29 23:31 UTCGHSA enrichment
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 22:48 UTCEG score recompute
  6. 2026-08-27 22:48 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 21:13 UTCEG score recompute
  9. 2026-08-26 21:13 UTCGHSA enrichment
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 18:55 UTCEG score recompute
  12. 2026-08-25 18:55 UTCGHSA enrichment
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 17:21 UTCEG score recompute▲ 0.70
  15. 2026-08-24 17:21 UTCGHSA enrichment
  16. 2026-08-24 17:18 UTCNVD updateCVSS v3 → 6.8
  17. 2026-08-24 05:40 UTCGHSA enrichment
  18. 2026-08-23 04:05 UTCGHSA enrichment
  19. 2026-08-22 02:30 UTCEG score recompute
  20. 2026-08-22 02:30 UTCGHSA enrichment
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 00:55 UTCEG score recompute
  23. 2026-08-21 00:55 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 23:21 UTCEG score recompute
Show 62 more
  1. 2026-08-19 23:21 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 21:45 UTCEG score recompute
  4. 2026-08-18 21:45 UTCGHSA enrichment
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 19:56 UTCEG score recompute
  7. 2026-08-17 19:56 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 18:01 UTCEG score recompute
  10. 2026-08-16 18:01 UTCGHSA enrichment
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 16:26 UTCEG score recompute
  14. 2026-08-15 16:26 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 14:51 UTCEG score recompute
  17. 2026-08-14 14:51 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 13:16 UTCEG score recompute
  20. 2026-08-13 13:16 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 11:42 UTCEG score recompute
  23. 2026-08-12 11:42 UTCGHSA enrichment
  24. 2026-08-11 10:07 UTCEG score recompute
  25. 2026-08-11 10:07 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 08:33 UTCEG score recompute
  28. 2026-08-10 08:33 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 06:58 UTCEG score recompute
  31. 2026-08-09 06:58 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 05:24 UTCEG score recompute
  34. 2026-08-08 05:24 UTCGHSA enrichment
  35. 2026-08-07 03:49 UTCEG score recompute
  36. 2026-08-07 03:49 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-06 02:14 UTCEG score recompute
  39. 2026-08-06 02:14 UTCGHSA enrichment
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-05 00:40 UTCEG score recompute
  42. 2026-08-05 00:40 UTCGHSA enrichment
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:39 UTCEPSS rescore
  45. 2026-08-03 23:05 UTCEG score recompute
  46. 2026-08-03 23:05 UTCGHSA enrichment
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 21:31 UTCEG score recompute
  49. 2026-08-02 21:31 UTCGHSA enrichment
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 19:56 UTCEG score recompute
  52. 2026-08-01 19:56 UTCGHSA enrichment
  53. 2026-08-01 04:16 UTCEPSS rescore
  54. 2026-07-31 18:21 UTCGHSA enrichment
  55. 2026-07-30 16:45 UTCEG score recompute
  56. 2026-07-30 16:45 UTCGHSA enrichment
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 01:30 UTCEPSS rescore
  59. 2026-07-29 22:01 UTCGHSA enrichment
  60. 2026-07-28 19:27 UTCEG score recompute
  61. 2026-07-28 18:24 UTCEG score recompute
  62. 2026-07-28 18:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50735?
CVE-2026-50735 is a medium vulnerability published on July 28, 2026. pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical…
When was CVE-2026-50735 disclosed?
CVE-2026-50735 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50735 actively exploited?
CVE-2026-50735 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 86.6% of all scored CVEs.
What is the CVSS score of CVE-2026-50735?
CVE-2026-50735 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-50735?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50735, 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-50735

Explore →

Is Your Infrastructure Affected by CVE-2026-50735?

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

Start Free Scan →Browse All CVEs