Skip to main content
VulnerabilityPublished Updated

CVE-2026-41035: Samba rsync · Improper Handling of Length Parameter Inconsistency

Affects Samba rsyncSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SambarsyncAffected
  • >=3.0.1 <=3.4.1
Fixed in–
GitHubrsyncproject/rsyncpkg:github/rsyncproject/rsyncOther threatsAffected
  • =3.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released security updates addressing this vulnerability, including patched rsync packages for Red Hat Enterprise Linux 6 Extended Lifecycle Support. Users should apply these official updates to remediate the issue. Since the vulnerability requires running rsync with the -X option, avoiding use of this option can reduce exposure but is not a complete mitigation. Patch status is confirmed by vendor advisories; therefore, applying the vendor-provided updates is the recommended remediation.

Description

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.

References

Community reviews

Loading reviews…