CVE-2026-53783

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-58090 (ENISA EUVD)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

October 24, 2026

Advisory Details (3)

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

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 advisoryMentions a patch (unverified)

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(3)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcostmanagement/costmanagement-ui-rhel10:17914608512026-10-08redhat
redhatrsync-0:3.1.3-28.el8_102026-09-30redhat
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 rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.7-1 ... 3.5.1+ds1-1 (32 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (13 versions)
  • every version up to 3.5.0+ds1-0+deb13u1: fixed in 3.5.0+ds1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions)
  • every version up to 3.5.0+ds1-1: fixed in 3.5.0+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 8× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53783?
CVE-2026-53783 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-53783 published?
The CVE record for CVE-2026-53783 was published on August 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-53783 actively exploited?
CVE-2026-53783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53783?
CVE-2026-53783 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-53783?
A fix for CVE-2026-53783 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53783 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-53783

Explore →

Is Your Infrastructure Affected by CVE-2026-53783?

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

Book a Demo →Browse All CVEs