CVE-2026-29518

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

Rsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file handling that allows attackers to redirect file writes outside intended directories by replacing parent directory components with symbolic links. Attackers with write access to a module path can exploit this race condition to create or overwrite arbitrary files, potentially modifying sensitive system files and achieving privilege escalation when the daemon runs with elevated privileges. This vulnerability can only be triggered if the chroot setting is false.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

May 20, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Patch available. Sources: github_pr, github_release.
generic

Rsync < 3.4.3 TOCTOU Race Condition Allows Symlink-Based Arbitrary File Write | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-toctou-race-condition-allows-symlink-based-arbitrary-file-write
generic

How my minimal, memory-safe Go rsync steers clear of vulnerabilities - Michael Stapelberg

https://michael.stapelberg.ch/posts/2026-05-24-minimal-memory-safe-go-rsync-vulns/
github_release Patch Available

v3.4.3

Patch available: RsyncProject/rsync v3.4.3

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

combined security fixes for 3.4.3 release

Patch available: RsyncProject/rsync v3.4.3 (PR #895 merged 2026-05-20)

https://github.com/RsyncProject/rsync/pull/895/changes/8471fdd1561049ef5f58df44a1811a50bd9a531d

Vendor Advisories for CVE-2026-29518(7)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntursync (3.1.2-2.1ubuntu1.6+esm3) @ bionic2026-08-25ubuntu
ubuntursync (3.4.1+ds1-5ubuntu1.2) @ questing2026-08-25ubuntu
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
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 rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.3-4, 3.2.3-4+deb11u1, 3.2.3-4+deb11u2, 3.2.3-4+deb11u33.2.3-4+deb11u4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1, 3.2.7-1+deb12u1, 3.2.7-1+deb12u2, 3.2.7-1+deb12u3, 3.2.7-1+deb12u43.2.7-1+deb12u5—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-5+deb13u1, 3.4.1+ds1-5+deb13u23.4.1+ds1-5+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.4.2+ds1-2 (6 versions)3.4.3+ds1-1—

Weakness Classification(1)

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 6× in last 7d / 46× 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 334 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-29518?
CVE-2026-29518 is a high vulnerability published on May 20, 2026. Rsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file handling that allows attackers to redirect file writes outside intended directories by replacing parent directory components with symbolic links. Attackers with write access to a module path…
When was CVE-2026-29518 disclosed?
CVE-2026-29518 was first published in the National Vulnerability Database 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-29518 actively exploited?
CVE-2026-29518 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-29518?
CVE-2026-29518 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-29518?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-29518, 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-29518

Explore →

Is Your Infrastructure Affected by CVE-2026-29518?

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

Start Free Scan →Browse All CVEs