CVE-2026-29518

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 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
4.9%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 15, 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(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-7ubuntu0.2) @ resolute2026-06-29ubuntu
ubuntursync (3.1.1-3ubuntu1.3+esm5) @ xenial2026-06-29ubuntu
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(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 15× in last 7d / 60× 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 185 total refreshes for this CVE.

  1. 2026-07-23 03:08 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-17 22:59 UTCOSV refresh
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-13 22:30 UTCEPSS rescore
  21. 2026-07-13 06:13 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:15 UTCEPSS rescore
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 20:29 UTCVendor advisory
  10. 2026-06-29 20:29 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 07:56 UTCVendor advisory
  16. 2026-06-28 07:56 UTCGHSA enrichment
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 20:15 UTCVendor advisory
  20. 2026-06-27 20:15 UTCGHSA enrichment
  21. 2026-06-27 07:26 UTCVendor advisory
  22. 2026-06-27 07:26 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 19:34 UTCVendor advisory
  25. 2026-06-26 19:34 UTCGHSA enrichment
  26. 2026-06-26 03:48 UTCVendor advisory
  27. 2026-06-26 03:48 UTCGHSA enrichment
  28. 2026-06-25 15:38 UTCVendor advisory
  29. 2026-06-25 15:38 UTCGHSA enrichment
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-24 14:05 UTCEPSS rescore
  33. 2026-06-24 14:05 UTCEPSS rescore
  34. 2026-06-23 21:33 UTCEPSS rescore
  35. 2026-06-23 21:32 UTCEPSS rescore
  36. 2026-06-22 14:25 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-21 01:59 UTCEPSS rescore
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-19 19:25 UTCEPSS rescore
  41. 2026-06-19 19:25 UTCEPSS rescore
  42. 2026-06-18 17:52 UTCEPSS rescore
  43. 2026-06-17 22:47 UTCVendor advisory
  44. 2026-06-17 22:47 UTCGHSA enrichment
  45. 2026-06-17 17:53 UTCEPSS rescore
  46. 2026-06-17 17:53 UTCEPSS rescore
  47. 2026-06-17 11:26 UTCVendor advisory
  48. 2026-06-17 11:26 UTCGHSA enrichment
  49. 2026-06-16 20:13 UTCVendor advisory
  50. 2026-06-16 20:13 UTCGHSA enrichment
  51. 2026-06-16 17:52 UTCEPSS rescore
  52. 2026-06-16 03:13 UTCVendor advisory
  53. 2026-06-16 03:13 UTCGHSA enrichment
  54. 2026-06-15 17:48 UTCEPSS rescore
  55. 2026-06-15 15:51 UTCVendor advisory
  56. 2026-06-15 15:51 UTCGHSA enrichment
  57. 2026-06-15 01:29 UTCVendor advisory
  58. 2026-06-15 01:29 UTCGHSA enrichment
  59. 2026-06-14 23:18 UTCEPSS rescore
  60. 2026-06-14 14:09 UTCVendor advisory
  61. 2026-06-14 14:09 UTCGHSA enrichment
  62. 2026-06-14 02:20 UTCVendor advisory
  63. 2026-06-14 02:20 UTCGHSA enrichment
  64. 2026-06-13 23:00 UTCEPSS rescore
  65. 2026-06-13 14:57 UTCVendor advisory
  66. 2026-06-13 14:57 UTCGHSA enrichment
  67. 2026-06-13 03:34 UTCVendor advisory
  68. 2026-06-13 03:34 UTCGHSA enrichment
  69. 2026-06-12 23:12 UTCEPSS rescore
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 15:45 UTCVendor advisory
  72. 2026-06-12 15:45 UTCGHSA enrichment
  73. 2026-06-12 04:07 UTCVendor advisory
  74. 2026-06-12 04:07 UTCGHSA enrichment
  75. 2026-06-11 16:46 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 July 15, 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 4.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-29518?
CVE-2026-29518 has a CVSS v3 base score of 7.0 (NVD).
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

Explore the affected products and dependency analysis for 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