Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-53803: rsync < 3.5.0 Symlink Following Arbitrary File Overwrite

CVE-2026-53803 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
7 (Red Hat)
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · base score 8.5, scored by VulnCheckAttack vector: local. Attack complexity: low. Attack requirements: none. Privileges required: low. User interaction: none. Confidentiality impact on the vulnerable system: high. Integrity impact on the vulnerable system: high. Availability impact on the vulnerable system: high. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-59 Improper Link Resolution Before File Access ('Link Following')
EPSS
0.23% chance of exploitation in the next 30 days (13th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
Fixed releases
  • Red Hat: 3.5.0, rsync-0:3.5.0-3.el10_2, rsync-0:3.1.3-28.el8_10, rsync-0:3.2.7-1.el9_8, openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0, costmanagement/costmanagement-ui-rhel10:1791460851 and 5 more in the advisory
Vendor advisories
2 from Red Hat, Veeam
Assigned by
VulnCheck (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-53803; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

rsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync's failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations.

Text from the CVE.org record (VulnCheck).

How do I fix CVE-2026-53803?

Upgrade to a fixed release named by the vendor:

  • Red Hat: 3.5.0, rsync-0:3.5.0-3.el10_2, rsync-0:3.1.3-28.el8_10, rsync-0:3.2.7-1.el9_8, openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0, costmanagement/costmanagement-ui-rhel10:1791460851
  • Do not run rsync setuid or point output paths (--log-file, --write-batch, or daemon config/log files) to user-writable directories like /tmp. While fs.protected_symlinks=1 prevents simple symlink creation in sticky directories on RHEL 7+, it does not stop parent-component attacks in standard directories. If the rsyncd daemon is unneeded, disable it (systemctl disable --now rsyncd); if required, enforce least-privilege execution and restrict network access to trusted hosts. (Red Hat)

Vendor advisories for CVE-2026-53803

Red Hat

1 advisory
  • Advisory severityHigh7.0

    High [CVE-2026-53803] Local Privilege Escalation via Symlink Following

    CVE-2026-53803Source published Source updated

    rsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync's failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations. This Important vulnerability in rsync allows a local attacker to achieve privilege escalation by exploiting a symlink following flaw. In Red Hat environments, the risk is elevated when rsync is configured to run with elevated privileges, such as setuid or in daemon…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 8
    • Red Hat Enterprise Linux 9
    • Red Hat OpenShift Container Platform 4.22

    5 more entries in the full advisory.

    Source-reported affected versions
    • < 3.5.0
    Source-reported fixed versions
    • 3.5.0
    • rsync-0:3.5.0-3.el10_2
    • rsync-0:3.1.3-28.el8_10
    • rsync-0:3.2.7-1.el9_8

    7 more entries in the full advisory.

    Mitigation guidance
    • Do not run rsync setuid or point output paths (--log-file, --write-batch, or daemon config/log files) to user-writable directories like /tmp. While fs.protected_symlinks=1 prevents simple symlink creation in sticky directories on RHEL 7+, it does not stop parent-component attacks in standard directories. If the rsyncd daemon is unneeded, disable it (systemctl disable --now rsyncd); if required, enforce least-privilege execution and restrict network access to trusted hosts.

Veeam

1 advisory
  • Advisory severityCritical

    Critical [CVE-2020-14040 +123] List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

    KB4825Source published

    This bulletin covers 124 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: Purpose This article aims to provide our customers' security and compliance teams with detailed information on security improvements. - Veeam Kasten for Kubernetes — Release Notes - Improved the protection of credentials used by block mode data mover operations and file recovery sessions. - Hardened the FileRecoverySession CR and file recovery pod with stricter input validation, restrictive mount options and a read-only SFTP service. - Passwords in proxy URLs are now masked in logs and the support bundle. - The multi-cluster proxy no longer forwards the caller's session and authentication credentials to secondary…

    Affected products in this advisory
    • Veeam Kasten for Kubernetes
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • 8.5.10
    • 8.5.5
    • 1.26.1
    • 8.5.3

    20 more entries in the full advisory.

    Mitigation guidance
    • List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Veeam Kasten for Kubernetes | 7 | 7.5 | 8 | 8.5 | 9 Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: 2026-11-16 Purpose This article describes all security-related fixes and improvements introduced in each release or update of Veeam Kasten for Kubernetes.
    • It is recommended to upgrade Veeam Kasten and to refresh the token by manually logging out.
    • Mitigation: Configure a bucket-level Default Object Lock retention so the object store stamps new objects at write time, or upgrade to Kasten 8.5.10.
    • Veeam Kasten for Kubernetes 8.5.5 Upgrade to Go 1.26.1 to address CVE-2026-25679 and CVE-2026-27142 Updated the UBI base image to address CVE-2026-4111 Veeam Kasten for Kubernetes 8.5.3 Upgrade to Go 1.25.7 to address CVE-2025-61732.

    4 more entries in the full advisory.

    Workarounds
    • Improved the protection of credentials used by block mode data mover operations and file recovery sessions.
    • Veeam Kasten for Kubernetes 8.0.14 Improved logging security for specific block mode datamover upload Pod invocations.

References

Timeline

  1. First vendor advisory listed by VulniPulse
  2. CVE record published
  3. CVE record last updated

All Red Hat advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat