CVE-2026-53783

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released 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: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

rsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer processing. Attackers can additionally leverage unrestricted flags such as --copy-unsafe-links, -D, and --log-file through rrsync to read or write files outside the permitted directory subtree.

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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
Patch available. Sources: github, github_release.
generic

rsync < 3.5.0 TOCTOU Race Condition Directory Escape via rrsync | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-toctou-race-condition-directory-escape-via-rrsync
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

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

rsync: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) · Advisory · RsyncProject/rsync · GitHub

Affected: 3.5.0. (Precise introduced-in ranges being finalised.)

https://github.com/RsyncProject/rsync/security/advisories/GHSA-9cgc-64g4-3gv5

Vendor Advisories for CVE-2026-53783(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrsync-0:3.2.7-1.el9_82026-09-14redhat
redhatrsync-0:3.5.0-3.el10_22026-09-14redhat

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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1 ... 3.5.0+ds1-2 (30 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.5.0+ds1-2 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions)3.5.0+ds1-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 18× in last 7d / 57× 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-09-19 03:03 UTCEG score recompute
  2. 2026-09-19 03:03 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 14:29 UTCVendor advisory
  5. 2026-09-18 01:53 UTCEG score recompute
  6. 2026-09-18 01:53 UTCVendor advisory
  7. 2026-09-17 13:19 UTCVendor advisory
  8. 2026-09-17 00:00 UTCEG score recompute
  9. 2026-09-17 00:00 UTCVendor advisory
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 10:47 UTCEG score recompute
  12. 2026-09-16 10:47 UTCVendor advisory
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 21:57 UTCVendor advisory
  15. 2026-09-15 09:23 UTCEG score recompute
  16. 2026-09-13 17:39 UTCEG score recompute
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-12 16:31 UTCEG score recompute
  19. 2026-09-11 15:22 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 14:14 UTCEG score recompute
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-09 09:31 UTCEG score recompute
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-07 18:18 UTCEG score recompute
Show 52 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 16:29 UTCEG score recompute
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-06 03:55 UTCEG score recompute
  5. 2026-09-05 02:25 UTCEG score recompute
  6. 2026-09-04 13:49 UTCEG score recompute
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 23:12 UTCEG score recompute
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-02 01:50 UTCEG score recompute
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-09-01 13:11 UTCEG score recompute
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 21:37 UTCEG score recompute
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 09:03 UTCEG score recompute
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-29 07:43 UTCEG score recompute
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 20:42 UTCEG score recompute
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 19:31 UTCEG score recompute
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 18:22 UTCEG score recompute
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-24 17:15 UTCEG score recompute
  27. 2026-08-23 03:28 UTCEG score recompute
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 02:20 UTCEG score recompute
  30. 2026-08-21 23:49 UTCEPSS rescore
  31. 2026-08-21 01:00 UTCEG score recompute
  32. 2026-08-20 22:55 UTCEPSS rescore
  33. 2026-08-19 23:54 UTCEG score recompute
  34. 2026-08-19 17:04 UTCEPSS rescore
  35. 2026-08-18 22:47 UTCEG score recompute
  36. 2026-08-18 13:48 UTCEPSS rescore
  37. 2026-08-17 21:36 UTCEG score recompute
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-16 20:29 UTCEG score recompute
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 07:55 UTCEG score recompute
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 06:48 UTCEG score recompute
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-14 17:34 UTCEG score recompute
  46. 2026-08-14 17:08 UTCEG score recompute
  47. 2026-08-14 16:32 UTCEG score recompute
  48. 2026-08-14 16:04 UTCEG score recompute
  49. 2026-08-14 13:14 UTCEG score recompute
  50. 2026-08-13 15:24 UTCEG score recompute
  51. 2026-08-13 15:13 UTCEG score recompute
  52. 2026-08-13 15:11 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53783?
CVE-2026-53783 is a high vulnerability published on August 13, 2026. rsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer…
When was CVE-2026-53783 disclosed?
CVE-2026-53783 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53783 actively exploited?
CVE-2026-53783 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 68.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53783?
CVE-2026-53783 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-53783?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53783, 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-53783

Explore →

Is Your Infrastructure Affected by CVE-2026-53783?

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

Start Free Scan →Browse All CVEs