CVE-2026-41035

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated 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.

In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are more widely vulnerable.

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
32%
KEV
Not listed

Published

April 16, 2026

Last Modified

August 27, 2026

Advisory Details (5)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

oss-security - Re: UAF in rsync 3.4.1 and below

http://www.openwall.com/lists/oss-security/2026/04/22/3
generic

oss-security - Re: UAF in rsync 3.4.1 and below

http://www.openwall.com/lists/oss-security/2026/04/16/9
generic

oss-security - UAF in rsync 3.4.1 and below

https://www.openwall.com/lists/oss-security/2026/04/16/2
generic

Releases · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/releases
generic

SIGSEGV in receive_xattr() on FreeBSD - qsort() called with wrong element count · Issue #871 · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/issues/871

Vendor Advisories for CVE-2026-41035(20)

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntursync (3.2.7-1ubuntu1.4) @ noble2026-08-27ubuntu
ubuntursync (3.1.1-3ubuntu1.3+esm5) @ xenial2026-08-27ubuntu
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatrhcos-414.92.202606231112-02026-07-01redhat
redhatrhcos-413.92.202606160406-02026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhcos-416.94.202606051757-02026-06-18redhat
redhatrhcos-418.94.202606051320-02026-06-17redhat
redhatrsync-0:3.1.3-12.el8_4.72026-06-11redhat
redhatrsync-0:3.1.3-20.el8_8.52026-06-11redhat
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrsync-0:3.1.3-14.el8_6.102026-06-11redhat
redhatrsync-0:3.1.2-12.el7_9.32026-06-11redhat
redhatrsync-0:3.0.6-12.el6_10.32026-06-11redhat
redhatrhcos-4.19.9.6.202606031700-02026-06-10redhat
redhatrsync-0:3.4.1-2.el10_0.22026-05-26redhat
redhatrsync-0:3.2.3-19.el9_2.32026-05-26redhat
redhatrsync-0:3.2.5-3.el9_6.12026-05-26redhat
redhatrsync-0:3.2.3-19.el9_4.32026-05-26redhat
redhatrsync-0:3.2.3-9.el9_0.52026-05-26redhat
redhatrsync-0:3.4.1-6.el10_22026-05-19redhat
redhatrsync-0:3.2.5-7.el9_82026-05-19redhat
redhatrsync-0:3.1.3-25.el8_102026-05-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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.1-r2—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.1-r2—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.1-r2—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.1-r2—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.1-r2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.3-4, 3.2.3-4+deb11u1, 3.2.3-4+deb11u2, 3.2.3-4+deb11u33.2.3-4+deb11u4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1, 3.2.7-1+deb12u1, 3.2.7-1+deb12u2, 3.2.7-1+deb12u3, 3.2.7-1+deb12u43.2.7-1+deb12u5—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-5+deb13u13.4.1+ds1-5+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-6, 3.4.1+ds1-7, 3.4.1+ds1-8~exp13.4.2+ds1-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

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 19× in last 7d / 87× 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 220 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41035?
CVE-2026-41035 is a high vulnerability published on April 16, 2026. In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are more widely…
When was CVE-2026-41035 disclosed?
CVE-2026-41035 was first published in the National Vulnerability Database on April 16, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41035 actively exploited?
CVE-2026-41035 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 67.7% of all scored CVEs.
What is the CVSS score of CVE-2026-41035?
CVE-2026-41035 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-41035?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41035, 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-41035

Explore →

Is Your Infrastructure Affected by CVE-2026-41035?

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

Start Free Scan →Browse All CVEs