CVE-2026-41035

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-16) is not newer than that change (2026-10-26), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-23215 (ENISA EUVD) · GHSA-m34r-4v3r-pp9v (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

April 16, 2026

Last Modified

October 26, 2026

Advisory Details (5)

Auto-updated Jun 14, 2026
Patch available.
Web page

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

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

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

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

oss-security - UAF in rsync 3.4.1 and below

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

Releases · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/releases
Web page

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(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntursync (3.4.1+ds1-7ubuntu0.2) @ resolute2026-10-25ubuntu
ubuntursync (3.1.2-2.1ubuntu1.6+esm3) @ bionic2026-10-25ubuntu
redhatopenshift/ose-rhel-coreos-8:412.86.202608241157-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-9:417.94.202606250942-02026-07-09redhat
redhatopenshift/ose-rhel-coreos-9:414.92.202606231112-02026-07-01redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202606160406-02026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202606051757-02026-06-18redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202606051320-02026-06-17redhat
redhatrsync-0:3.1.3-14.el8_6.102026-06-11redhat
redhatrsync-0:3.1.3-20.el8_8.52026-06-11redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202606030318-02026-06-11redhat
redhatrsync-0:3.1.2-12.el7_9.32026-06-11redhat
redhatrsync-0:3.0.6-12.el6_10.32026-06-11redhat
redhatrsync-0:3.1.3-12.el8_4.72026-06-11redhat
redhatopenshift/ose-rhel-coreos-9: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 rangeFix by version rangeDependents
rsync—
  • 3.0.1 up to 3.4.1-r2: fixed in 3.4.1-r2
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.0.1 up to 3.4.1-r2: fixed in 3.4.1-r2
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.0.1 up to 3.4.1-r2: fixed in 3.4.1-r2
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.0.1 up to 3.4.1-r2: fixed in 3.4.1-r2
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.0.1 up to 3.4.1-r2: fixed in 3.4.1-r2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.3-4, 3.2.3-4+deb11u1, 3.2.3-4+deb11u2, 3.2.3-4+deb11u3
  • every version up to 3.2.3-4+deb11u4: fixed in 3.2.3-4+deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.7-1, 3.2.7-1+deb12u1, 3.2.7-1+deb12u2, 3.2.7-1+deb12u3, 3.2.7-1+deb12u4
  • every version up to 3.2.7-1+deb12u5: fixed in 3.2.7-1+deb12u5
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-5+deb13u1
  • every version up to 3.4.1+ds1-5+deb13u2: fixed in 3.4.1+ds1-5+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-6, 3.4.1+ds1-7, 3.4.1+ds1-8~exp1
  • every version up to 3.4.2+ds1-1: fixed in 3.4.2+ds1-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

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 10× in last 7d / 46× 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.

Showing the most recent 100 of 298 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 198 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41035?
CVE-2026-41035 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-41035 published?
The CVE record for CVE-2026-41035 was published on April 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-41035 actively exploited?
CVE-2026-41035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-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?
A fix for CVE-2026-41035 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41035 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-41035

Explore →

Is Your Infrastructure Affected by CVE-2026-41035?

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

Book a Demo →Browse All CVEs