Skip to main content
Mallory
CriticalVulnerability

CVE-2026-70452: rsync Hostname-Based Access Control Bypass via DNS Resolution Failure

Published Aug 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 2 in a dayToday
CVSS9.1Critical · v4
EPSS0.44%39th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Samba
IdentifiersCVE-2026-70452CWE-636 · Not Failing Securely ('Failing…

CVE-2026-70452 is a fail-open access-control vulnerability in the rsync daemon affecting versions 3.1.0 through versions before 3.5.0. During evaluation of hostname-based hosts deny rules, a failed DNS lookup causes the daemon to skip the affected rule instead of denying access. Remote attackers capable of inducing the relevant DNS resolution failures can bypass module-level host restrictions and gain unauthorized access to restricted module file trees.

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 exposes restricted module file trees to clients that hostname-based deny rules should block. This can compromise confidentiality through unauthorized file access and integrity through file modification where module permissions permit writes. The vulnerability-specific assessments indicate high confidentiality and integrity impacts and no availability impact. The flaw does not establish a bypass of independent module authentication or filesystem permissions.

Mitigation

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

As a compensating control, restrict access to the rsync daemon using firewall or network ACL rules based on explicitly authorized IP addresses, independently of hostname resolution. Avoid relying solely on hostname-based deny rules to protect sensitive modules. No vendor-specific temporary workaround is identified.

Remediation

Patch, then assume compromise.

Upgrade rsync to version 3.5.0 or later, or install a distribution security update that backports the fix. Update rsync-daemon packages where separately packaged. For Debian stable (trixie), install rsync 3.5.0+ds1-0+deb13u1 or a later security-updated version. Photon OS 5.0 security updates provide rsync 3.5.0-1.ph5.

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-70452 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-70452 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-70452?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-70452.
Is there a patch for CVE-2026-70452?
Upgrade rsync to version 3.5.0 or later, or install a distribution security update that backports the fix. Update rsync-daemon packages where separately packaged.
What products are affected by CVE-2026-70452?
Samba Rsync.
How severe is CVE-2026-70452?
CVE-2026-70452 has a CVSS v4 score of 9.1 (Critical) and an EPSS score of 0.44% (39th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+30 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity4Community discussion across Reddit, Mastodon, and other social sources.