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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

May 20, 2026

Last Modified

September 1, 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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntursync (3.4.1+ds1-7ubuntu0.2) @ resolute2026-08-25ubuntu
ubuntursync (3.1.2-2.1ubuntu1.6+esm3) @ bionic2026-08-25ubuntu
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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.4.3-r0: fixed in 3.4.3-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.4.3-r0: fixed in 3.4.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.4.3-r0: fixed in 3.4.3-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.4.3-r0: fixed in 3.4.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.4.3-r0: fixed in 3.4.3-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.3-4, 3.2.3-4+deb11u1, 3.2.3-4+deb11u2, 3.2.3-4+deb11u3
  • every version up to 3.2.3-4+deb11u4: fixed in 3.2.3-4+deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.7-1, 3.2.7-1+deb12u1, 3.2.7-1+deb12u2, 3.2.7-1+deb12u3, 3.2.7-1+deb12u4
  • every version up to 3.2.7-1+deb12u5: fixed in 3.2.7-1+deb12u5
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-5+deb13u1, 3.4.1+ds1-5+deb13u2
  • every version up to 3.4.1+ds1-5+deb13u3: fixed in 3.4.1+ds1-5+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.2+ds1-2 (6 versions)
  • every version up to 3.4.3+ds1-1: fixed in 3.4.3+ds1-1
—

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 4× in last 7d / 21× 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 305 total refreshes for this CVE.

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

Related CVEs(same product + 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 on May 20, 2026, with the most recent update on September 1, 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 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43618?
CVE-2026-43618 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-43618?
A fix for CVE-2026-43618 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43618 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-43618

Explore →

Is Your Infrastructure Affected by CVE-2026-43618?

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

Book a Demo →Browse All CVEs