Skip to content
VulniPulse
Critical 3 vendors · 3 advisories

CVE-2026-53791: rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header

CVE-2026-53791 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
9.1 (NetApp), 7.4 (Red Hat)
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · base score 9.1, scored by VulnCheckAttack vector: network. Attack complexity: low. Attack requirements: present. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: high. Integrity impact on the vulnerable system: high. Availability impact on the vulnerable system: none. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-290 Authentication Bypass by Spoofing
EPSS
0.50% chance of exploitation in the next 30 days (43rd percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: 3.5.0, rsync-0:3.5.0-3.el10_2, rsync-0:3.2.7-1.el9_8, openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0, costmanagement/costmanagement-ui-rhel10:1791460851, RHSA-2026:67463 and 3 more in the advisory
Vendor advisories
3 from NetApp, 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-53791; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

rsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address.

Text from the CVE.org record (VulnCheck).

How do I fix CVE-2026-53791?

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.2.7-1.el9_8, openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0, costmanagement/costmanagement-ui-rhel10:1791460851, RHSA-2026:67463
  • Restrict rsync daemon TCP/873 to the trusted proxy only (CME-202). If PROXY protocol is unused, leave proxy protocol disabled (the default). (Red Hat)

Vendor advisories for CVE-2026-53791

NetApp

1 advisory
  • Advisory severityCritical9.1

    Critical [CVE-2026-53791] Rsync Vulnerability in NetApp Products

    NTAP-20261104-0005Source published Source updated

    Rsync versions through 3.4.4 are susceptible to a vulnerability which when successfully exploited could allow an attacker that can connect directly to the rsync daemon to inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address. Successful exploitation of this vulnerability could lead to disclosure of sensitive information or addition or modification of data. NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 3.4.4
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh7.4

    High [CVE-2026-53791] rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header

    CVE-2026-53791Source published Source updated

    rsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address. This allows unauthorized access to restricted resources. Note: Red Hat Enterprise Linux 8 and earlier versions do not contain the vulnerable PROXY protocol implementation and are not affected. Red Hat severity: Important — CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). Weakness: CWE-290. Affected Red Hat…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 9
    • Red Hat OpenShift Container Platform 4.22
    • Red Hat Cost Management On-Premise 1

    1 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.2.7-1.el9_8
    • openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0

    5 more entries in the full advisory.

    Mitigation guidance
    • Restrict rsync daemon TCP/873 to the trusted proxy only (CME-202). If PROXY protocol is unused, leave proxy protocol disabled (the default).

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 NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp'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 NetApp