CVE Tools

CVE-2026-119741

rsync < 3.5.2 Denial of Service via hash_search() Checksum Collisions

No known exploitation. EPSS puts it in the 50th percentile. Fixed in 3.5.2.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • RsyncProject rsyncAffected: ≤ 3.5.1Upgrade to: after 3.5.1Fixed builds3.5.2Stated by: CVE record
  • Samba RsyncAffected: ≤ 3.5.1Upgrade to: after 3.5.1Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run an rsync daemon (rsyncd) that is reachable from the internet, especially one allowing anonymous/public module access.
  2. If you don't run an rsync daemon, or only use rsync over SSH to systems you control, you are not exposed to this issue.
  3. Upgrade rsync to version 3.5.2 or later, which fixes the checksum-collision handling.
  4. If upgrading isn't immediately possible, restrict access to the rsync daemon (firewall rules, require authentication, or disable public/anonymous modules) until patched.
  5. Restart the rsync daemon after upgrading and confirm the version with rsync --version.

What it is

From the CVE record

rsync before 3.5.2 contains a denial of service vulnerability in the delta-transfer sender's hash_search() in match.c that allows malicious receivers to trigger unbounded strong-checksum work at consecutive offsets. Unauthenticated attackers pulling from a public daemon module can supply weak checksums colliding with consecutive rolling windows plus non-matching strong checksums, exhausting sender CPU across concurrent connections.

In plain language

Written by AI from the record

A bug in rsync (versions before 3.5.2) lets someone pulling files from a public rsync server make that server work so hard it slows to a crawl or stops responding; update to 3.5.2 if you run a public rsync server.

CWE-407 (algorithmic complexity/resource exhaustion) in rsync's delta-transfer sender hash_search() allows unauthenticated clients connected to a public rsync daemon module to craft colliding weak checksums that force unbounded strong-checksum computation across concurrent connections, causing CPU exhaustion/DoS on the sender.

If you're affected

  • Rsync server becomes unresponsive
  • File transfer/backup service disruption
  • Server CPU exhaustion
  • Possible downtime for dependent services

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS50th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 1 day, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablepublished, weakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Rsync, not every advisory.