Skip to main content
Mallory
CriticalVulnerability

CVE-2026-53791: rsync Daemon IP Access-Control Bypass via PROXY Protocol Spoofing

Published Aug 13, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS9.1Critical · v4
EPSS0.50%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Samba
IdentifiersCVE-2026-53791CWE-290 · Authentication Bypass by Spoofing

CVE-2026-53791 is an IP address spoofing vulnerability in rsync daemons before version 3.5.0. An unauthenticated remote attacker who can connect directly to a vulnerable daemon can submit a crafted PROXY protocol header containing a forged source address. The daemon uses the attacker-supplied address when evaluating hosts allow/deny rules, allowing the attacker to bypass IP-based restrictions that would reject the actual source address.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation defeats source-IP access restrictions and permits unauthorized access to rsync resources otherwise blocked by hosts allow/deny rules. This can expose confidential files and permit modification of data where the affected modules allow writing, subject to remaining authentication and filesystem permissions. The vulnerability is assessed as having high confidentiality and integrity impacts and no availability impact; it does not establish a bypass of independent authentication controls.

Mitigation

If you can’t patch tonight, do this now.

Until patched, prevent untrusted clients from connecting directly to the rsync daemon by enforcing source restrictions at a firewall or equivalent network control. Where a PROXY-protocol-aware frontend is used, restrict backend daemon connections to that trusted frontend and ensure clients cannot bypass it. Do not rely solely on the vulnerable daemon's hosts allow/deny rules. No vendor-specific temporary workaround is identified.

Remediation

Patch, then assume compromise.

Upgrade to rsync 3.5.0 or later, or install the distribution's security-fixed package containing the backported fix. Identified fixed packages include Debian trixie version 3.5.0+ds1-0+deb13u1, Photon OS version 3.5.0-1.ph5, RHEL 10 version 3.5.0-3.el10_2, and RHEL 9 version 3.2.7-1.el9_8. Use distribution-specific security advisories to verify fixed package versions rather than relying solely on the upstream version number.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SambaRsyncapplication
FAQ

Frequently asked questions

Is CVE-2026-53791 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-53791 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53791?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-53791.
Is there a patch for CVE-2026-53791?
Upgrade to rsync 3.5.0 or later, or install the distribution's security-fixed package containing the backported fix. Identified fixed packages include Debian trixie version 3.5.0+ds1-0+deb13u1, Photon OS version 3.5.0-1.ph5, RHEL 10 version 3.5.0-3.el10_2, and RHEL 9 version 3.2.7-1.el9_8.
What products are affected by CVE-2026-53791?
Samba Rsync.
How severe is CVE-2026-53791?
CVE-2026-53791 has a CVSS v4 score of 9.1 (Critical) and an EPSS score of 0.50% (44th percentile) as of Nov 14, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.