Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityproof-of-concept-release

Use-After-Free Flaw in rsync Xattr Handling Exposes Receivers to Heap Corruption

Vulnerability Disclosure · 4 sources · Updated 5mo ago · First seen Apr 16, 2026

Use-After-Free Flaw in rsync Xattr Handling Exposes Receivers to Heap Corruption

A publicly disclosed vulnerability in rsync affects versions 3.0.1 through 3.4.1, as well as the 3.4.2 development head, due to a use-after-free bug in the receive_xattr() function. The flaw occurs because rsync uses a wire-supplied extended-attribute count as the length for qsort() instead of the number of accepted xattrs, which can pull stale entries from prior files into the current file's xattr list. A malicious rsync sender can trigger dangling pointers, read-after-free, double-free, heap corruption, information disclosure, and denial of service in the receiving process over the network.

The bug was traced to commit d724dd186, introduced during development of rsync 3.0.1pre1 in 2008 when sorting was added after namespace prefix munging for --fake-super mode. On Linux, exploitation requires --xattrs together with --fake-super or certain xattr filter configurations, while on FreeBSD, macOS, and other non-Linux platforms, any use of -X/--xattrs is vulnerable. The reported fix is to replace the qsort() count argument with temp_xattr.count, while public discussion on oss-sec also raised questions about whether and when rsync maintainers had been notified before disclosure.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Mar 7, 2008 – Apr 16, 2026
  1. Apr 16, 20267mo ago

    Rsync UAF issue linked to CVE-2026-41035

    In follow-up oss-sec discussion, Salvatore Bonaccorso said the rsync use-after-free vulnerability appeared to have been assigned CVE-2026-41035 and pointed to the public CVE record. This added a formal vulnerability identifier to the previously disclosed flaw.

    oss-sec: Re: UAF in rsync 3.4.1 and below
  2. Apr 16, 20267mo ago

    Public discussion raises maintainer notification questions

    In follow-up discussion on oss-sec, Alan Coopersmith asked whether rsync maintainers had been notified and when that notification occurred. The exchange indicated that disclosure coordination details were still unresolved in the public thread.

  3. Apr 16, 20267mo ago

    Use-after-free flaw in rsync publicly reported on oss-sec

    Przemyslaw Frasunek disclosed a use-after-free vulnerability in rsync's receive_xattr() function, explaining that a wire-supplied xattr count was used as the qsort() length instead of the actual accepted xattr count. The report said this could cause dangling pointers, double-free, heap corruption, information disclosure, and denial of service when a malicious sender targets a receiver using extended attributes.

  4. Mar 7, 200819y ago

    Bug introduced into rsync receive_xattr() during 3.0.1pre1 development

    A vulnerable change was introduced in commit d724dd186, adding qsort() handling in receive_xattr() during development of rsync 3.0.1pre1. This change created the use-after-free condition later reported as affecting rsync 3.0.1 through 3.4.1 and the 3.4.2 development head.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Rsync
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.