CVE-2026-53800

Description

A Time-of-Check Time-of-Use (TOCTOU) race condition in rsync's --remove-source-files option allows a local attacker to delete arbitrary files. By replacing a source file with a symlink immediately after transfer but before deletion, the attacker can force rsync to delete the symlink target, resulting in data loss or system instability.

Statement

An attacker with local access and the ability to create symlinks can exploit a Moderate severity symlink race condition in rsync to delete arbitrary files. This is achieved by altering the symlink target during an active file transfer. Because the flaw stems directly from the --remove-source-files feature, the vulnerability is limited to specific operational scenarios where that option is used.

Mitigation

Do not use --remove-source-files; the unlink path is unused unless that option is enabled. If rsyncd is in use, add remove-source-files to refuse options so clients cannot turn it on. If the option is required, ensure no untrusted user can create or replace directories in the source tree, and do not run rsync as root over such a tree.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.7N/A4.7
Attack VectorLocalN/ALocal
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Alter Execution Logic; Unexpected State

The attacker can gain access to otherwise unauthorized resources.

Integrity,Other

Technical Impact: Modify Application Data; Modify Files or Directories; Modify Memory; Other

Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.

Integrity,Other

Technical Impact: Other

The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.

Non-Repudiation

Technical Impact: Hide Activities

If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.

Non-Repudiation,Other

Technical Impact: Other

In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.

Other

Technical Impact: Unexpected State

The product may perform invalid actions when the resource is in an unexpected state.

Frequently Asked Questions

Want to get errata notifications? Sign up here.