CVE-2026-41035

HIGHNVD 7.87.4▼
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-04-16. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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.4(medium)
EPSS
31.5%
KEV
Not listed

Published

April 16, 2026

Last Modified

July 15, 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(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntursync (3.4.1+ds1-5ubuntu1.2) @ questing2026-06-14ubuntu
ubuntursync (3.1.3-8ubuntu0.9+esm1) @ focal2026-06-14ubuntu
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrsync-0:3.1.3-12.el8_4.72026-06-11redhat
redhatrsync-0:3.1.3-20.el8_8.52026-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.

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 13× in last 7d / 42× 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 131 total refreshes for this CVE.

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

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 July 15, 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 31.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41035?
CVE-2026-41035 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
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

Explore the affected products and dependency analysis for 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