CVE-2026-53803

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

rsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync's failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations.

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

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 Symlink Following Arbitrary File Overwrite | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-symlink-following-arbitrary-file-overwrite
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: arbitrary file write / privilege escalation via symlinked operator-supplied output paths · Advisory · RsyncProject/rsync · GitHub

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

https://github.com/RsyncProject/rsync/security/advisories/GHSA-g9f4-7q66-9582

Vendor Advisories for CVE-2026-53803(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.5.0-3.el10_22026-09-14redhat
redhatrsync-0:3.2.7-1.el9_82026-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(1)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53803?
CVE-2026-53803 is a high vulnerability published on August 13, 2026. rsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync's failure to reject…
When was CVE-2026-53803 disclosed?
CVE-2026-53803 was first published in the National Vulnerability Database 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-53803 actively exploited?
CVE-2026-53803 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 85.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53803?
CVE-2026-53803 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53803?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53803, 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-53803

Explore →

Is Your Infrastructure Affected by CVE-2026-53803?

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

Start Free Scan →Browse All CVEs