CVE-2026-43618

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory published 2026-05-20. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receiver process to read and return data from outside the intended buffer bounds. Attackers can exploit this vulnerability to disclose process memory contents including environment variables, passwords, heap and stack data, and library memory pointers, significantly reducing ASLR effectiveness and facilitating further exploitation.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated May 20, 2026
Patch available. Sources: github.
generic

Rsync < 3.4.3 Integer Overflow Information Disclosure | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-integer-overflow-information-disclosure
github Patch Available

rsync: Integer overflow in compressed-token decoding enables remote memory dump · Advisory · RsyncProject/rsync · GitHub

Affected: 3.4.3

https://github.com/RsyncProject/rsync/security/advisories/GHSA-g37v-g3gj-pmwq
generic

Release v3.4.3 · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/releases/tag/v3.4.3

Vendor Advisories for CVE-2026-43618(6)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntursync (3.4.1+ds1-5ubuntu1.2) @ questing2026-07-26ubuntu
ubuntursync (3.1.1-3ubuntu1.3+esm5) @ xenial2026-07-26ubuntu
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrsync-0:3.4.4-1.el10_22026-06-16redhat
redhatrsync-0:3.1.3-27.el8_102026-06-16redhat
redhatrsync-0:3.2.5-7.el9_8.22026-06-16redhat

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.

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 13× in last 7d / 42× 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 169 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43618?
CVE-2026-43618 is a high vulnerability published on May 20, 2026. Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receiver process to read and return data from outside the intended…
When was CVE-2026-43618 disclosed?
CVE-2026-43618 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 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-43618 actively exploited?
CVE-2026-43618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43618?
CVE-2026-43618 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-43618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43618, 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

Explore the affected products and dependency analysis for CVE-2026-43618

Explore →

Is Your Infrastructure Affected by CVE-2026-43618?

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

Start Free Scan →Browse All CVEs