Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-41035: Use-after-free in rsync extended-attribute handling

Published Apr 16, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS7.8High · v3.1
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Samba
IdentifiersCVE-2026-41035CWE-416

CVE-2026-41035 is a receiver-side use-after-free vulnerability in rsync versions 3.0.1 through 3.4.1. The receive_xattr function relies on an untrusted length value during a qsort call while processing extended attributes, allowing a malicious rsync peer to trigger memory corruption in the receiving process. Exposure requires the victim to run rsync with -X or --xattrs. Many, but not all, common Linux configurations are vulnerable; non-Linux platforms are more widely affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation causes use-after-free memory corruption in the receiving rsync process, potentially disrupting transfers or compromising the process. The assigned CVSS v3.0 score is 7.8, with high confidentiality, integrity, and availability impacts. Specific mechanisms for achieving code execution or information disclosure are not established by the available technical details. Exploits are reported as available, but active exploitation is not established.

Mitigation

If you can’t patch tonight, do this now.

Avoid -X and --xattrs until a fixed package is deployed, particularly when synchronizing with untrusted or potentially compromised peers. If extended-attribute preservation is essential, restrict synchronization to trusted peers as an exposure-reduction measure rather than a complete fix.

Remediation

Patch, then assume compromise.

Install the vendor security update for the applicable operating-system release and support channel. Confirmed fixed RHEL package builds include 3.1.3-25.el8_10 for RHEL 8.10, 3.2.3-19.el9_2.3 for RHEL 9.2, 3.2.3-19.el9_4.3 for RHEL 9.4, 3.2.5-3.el9_6.1 for RHEL 9.6, and 3.4.1-2.el10_0.2 for RHEL 10.0. These builds contain backported fixes, so the upstream version number alone does not establish vulnerability status. Update affected container images and rebuild dependent images. An upstream fixed release is not specified in the available vulnerability details.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SambaRsyncapplication
FAQ

Frequently asked questions

Is CVE-2026-41035 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-41035 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41035?
Yes. As of Nov 11, 2026, Mallory has reports of a public exploit for CVE-2026-41035.
Is there a patch for CVE-2026-41035?
Install the vendor security update for the applicable operating-system release and support channel. Confirmed fixed RHEL package builds include 3.1.3-25.el8_10 for RHEL 8.10, 3.2.3-19.el9_2.3 for RHEL 9.2, 3.2.3-19.el9_4.3 for RHEL 9.4, 3.2.5-3.el9_6.1 for RHEL 9.6, and 3.4.1-2.el10_0.2 for RHEL 10.0.
What products are affected by CVE-2026-41035?
Samba Rsync.
How severe is CVE-2026-41035?
CVE-2026-41035 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.41% (36th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

45 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : rsync (EulerOS-SA-2026-4729) | Tenable®A receiver-side use-after-free in rsync 3.0.1 through 3.4.1 results from an untrusted length used during a qsort call in receive_xattr. Exploitation requires extended-attribute processing with -X or --xattrs. The description states that many Linux configurations and a broader range of non-Linux configurations are vulnerable.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : rsync (EulerOS-SA-2026-4671) | Tenable®A receiver-side use-after-free in rsync 3.0.1 through 3.4.1 results from using an untrusted length during sorting in receive_xattr. Exploitation requires extended-attribute processing through -X or --xattrs. The advisory states that many Linux configurations and a broader range of non-Linux configurations are vulnerable.Read more ↗tenable nessus pluginsNews · Oct 12, 2026EulerOS 2.0 SP11 : rsync (EulerOS-SA-2026-4376) | Tenable®A receiver-side use-after-free vulnerability in rsync versions 3.0.1 through 3.4.1, caused by an untrusted length value used during a qsort call in receive_xattr. Exploitation requires the victim to run rsync with extended attributes enabled (-X or --xattrs). Many Linux configurations and a broader range of non-Linux configurations are vulnerable. The advisory identifies affected rsync packages on EulerOS 2.0 SP11 and assigns a CVSS v3 base score of 7.8. Nessus detects affected versions using self-reported version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 12, 2026EulerOS 2.0 SP11 : rsync (EulerOS-SA-2026-4286) | Tenable®A receiver-side use-after-free vulnerability in rsync versions 3.0.1 through 3.4.1, caused by an untrusted length used during a qsort call in receive_xattr. Exposure requires running rsync with -X/--xattrs. The advisory identifies affected rsync packages on EulerOS 2.0 SP11 and assigns a CVSS v3 base score of 7.8 (High). Nessus detects affected versions using self-reported version information rather than testing exploitation.Read more ↗
+30 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.