CVE-2026-29518

High
7.0
0.05.010.0
Year
2026
Published
May 20, 2026
Known Affected Devices
0
CVSS Score
7.0

What is CVE-2026-29518?

Rsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file handling that allows attackers to redirect file writes outside intended directories by replacing parent directory components with symbolic links. Attackers with write access to a module path can exploit this race condition to create or overwrite arbitrary files, potentially modifying sensitive system files and achieving privilege escalation when the daemon runs with elevated privileges. This vulnerability can only be triggered if the chroot setting is false.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
AV
Attack Vector
Local

Requires local access — attacker must be logged in or have physical access to the device.

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
Low

Basic user account required (e.g. standard login without admin rights).

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
High

Complete loss of confidentiality. All data on the component may be exposed.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
High

Complete denial of service. The component becomes fully unavailable.

FAQ

How severe is CVE-2026-29518?

CVE-2026-29518 has a CVSS score of 7.0/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.

What does the CVSS score mean for CVE-2026-29518?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-29518 scores 7.0/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2026-29518?

The list of devices confirmed to be affected by CVE-2026-29518 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2026-29518?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.