LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41035: In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leadin...

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.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Rsync can mishandle extended-attribute data from an untrusted sender, causing a use-after-free on the receiving side. Exposure depends on running affected rsync versions with -X or --xattrs. The business risk is highest where rsync accepts data from users, partners, automation, or less-trusted systems.

Executive priority

Treat as a high-priority patch and configuration review for backup, deployment, and file-transfer infrastructure. Prioritize exposed receivers, non-Linux systems, and workflows accepting data from less-trusted users or systems.

Technical view

CVE-2026-41035 affects rsync 3.0.1 through 3.4.1. receive_xattr trusts a length value used during qsort, leading to a receiver-side use-after-free. CVSS 3.1 is 7.4 high, with network attack vector, low complexity, low privileges, no user interaction, and changed scope.

Likely exposure

Systems using rsync with -X or --xattrs are the relevant exposure. Linux impact varies by configuration; non-Linux platforms are described as more widely vulnerable. Internet-facing or multi-tenant rsync receivers deserve priority review.

Exploitation context

The provided bundle does not establish active exploitation, and KEV is false. The vulnerability is reachable over networked rsync workflows where an attacker can influence transferred extended attributes and the receiver preserves them.

Researcher notes

The key constraints are receiver role, affected version range, and xattr preservation. Evidence provided does not name a universal fix version, so remediation should follow upstream release notes and vendor advisories. Avoid assuming all Linux deployments are exploitable.

Mitigation direction

  • Identify rsync receivers running affected versions with --xattrs enabled.
  • Apply vendor rsync updates or supported backports for CVE-2026-41035.
  • Disable --xattrs where business workflows do not require it.
  • Restrict rsync access to trusted users, hosts, and networks.
  • Review Red Hat advisories for affected enterprise packages.

Validation and detection

  • Inventory rsync versions across servers, appliances, containers, and backup jobs.
  • Search job definitions for -X or --xattrs usage.
  • Confirm whether rsync receives data from untrusted or semi-trusted sources.
  • Check vendor advisory status for each operating system build.
  • Retest backup and sync workflows after updating or disabling xattrs.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-130: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-805: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
3ADP providers
28Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7mitre
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-41035Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
redhat-SADPrsync: Rsync: Use-after-free vulnerability in extended attribute handling
other:Red Hat severity ratingcvssV3_1
  • 2026-04-16T08:00:54.200Z: Reported to Red Hat.
  • 2026-04-16T06:53:05.237Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Sambarsync3.0.1unknown
Weakness

CWE details

CWE-130CWE-805

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.