CVE-2026-53799

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st 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
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

August 31, 2026

Advisory Details (3)

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

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

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

Vendor Advisories for CVE-2026-53799(1)

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

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.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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.

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

Frequently asked(5)

What is CVE-2026-53799?
CVE-2026-53799 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-53799 was made public on August 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 13, 2026. EchelonGraph's copy of the record carries a last-modified date of August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-53799 actively exploited?
CVE-2026-53799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53799?
CVE-2026-53799 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53799?
A fix for CVE-2026-53799 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53799 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-53799

Explore →

Is Your Infrastructure Affected by CVE-2026-53799?

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