CVE-2026-53799

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

rsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent acl_set_file() or lsetxattr() call. Attackers can exploit this timing window to redirect ACL and xattr application through a crafted symlink to files outside the intended destination tree, potentially granting elevated permissions and enabling local privilege escalation.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
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 Race Condition via ACL/xattr Application | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-symlink-race-condition-via-acl-xattr-application
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: receiver ACL/xattr metadata apply follows a symlink race -> arbitrary ACL set (local privilege escalation) · Advisory · RsyncProject/rsync · GitHub

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

https://github.com/RsyncProject/rsync/security/advisories/GHSA-phxh-hjqv-39c9

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.

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53799?
CVE-2026-53799 is a medium vulnerability published on August 13, 2026. rsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent aclsetfile() or…
When was CVE-2026-53799 disclosed?
CVE-2026-53799 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-53799 actively exploited?
CVE-2026-53799 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53799?
CVE-2026-53799 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-53799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53799, 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-53799

Explore →

Is Your Infrastructure Affected by CVE-2026-53799?

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

Start Free Scan →Browse All CVEs