CVE-2026-53802

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). 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 — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

rsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a symlink at a predictable --files-from or --password-file path, or supply a --files-from path that escapes the daemon module root, to read arbitrary files accessible to the rsync process.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

August 31, 2026

Advisory Details (3)

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

rsync < 3.5.0 Arbitrary File Read via Symlink Following | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-arbitrary-file-read-via-symlink-following
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
githubMentions a patch (unverified)

rsync: arbitrary file read / transfer-shaping via symlinked operator-supplied input files · Advisory · RsyncProject/rsync · GitHub

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

https://github.com/RsyncProject/rsync/security/advisories/GHSA-4mfr-8jrv-49x4

Vendor Advisories for CVE-2026-53802(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
redhatrsync-0:3.1.3-28.el8_102026-09-30redhat
redhatrhcos-4.22.9.8.202609221802-02026-09-29redhat
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(1)

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

Additional Vendor Advisories

(3)

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 17× in last 7d / 82× 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 134 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-53802?
CVE-2026-53802 is a high vulnerability published on August 13, 2026. rsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a…
When was CVE-2026-53802 disclosed?
CVE-2026-53802 was first published on August 13, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53802 actively exploited?
CVE-2026-53802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53802?
CVE-2026-53802 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53802?
A fix for CVE-2026-53802 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53802 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-53802

Explore →

Is Your Infrastructure Affected by CVE-2026-53802?

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

Book a Demo →Browse All CVEs