Vulnerability DatabaseCVE-2026-119741

CVE-2026-119741: 
rsync vulnerability analysis and mitigation

Overview

CVE-2026-119741 is a denial-of-service vulnerability in rsync's delta-transfer sender, specifically in the hash_search() function within match.c. Unauthenticated attackers pulling from a public rsync daemon module can supply crafted weak checksums that collide with consecutive rolling windows combined with non-matching strong checksums, forcing the sender to compute unbounded strong-checksum (get_checksum2()) work at every byte offset — an O(N×B) CPU exhaustion attack. Affected versions include rsync up to and including 3.5.1 (and the 3.2.x line up to 3.2.7); versions 3.5.2 and 3.2.8 are unaffected. The vulnerability was published on November 3, 2026, and is classified as CWE-407 (Inefficient Algorithmic Complexity). It carries a CVSS v3.1 base score of 7.5 (High) and a CVSS v4.0 base score of 8.7 (High) (GitHub PR #1132, Microsoft MSRC).

Technical details

The root cause is an inefficient algorithmic complexity flaw (CWE-407) in hash_search() in match.c. When a malicious receiver sends weak checksums that collide with the sender's rolling Adler-32 windows but whose strong checksums (get_checksum2()) do not match any basis block, the sender falls back to a 1-byte sliding walk and recomputes a full strong checksum (up to 128 KiB) at every single byte offset — resulting in O(N×B) CPU work rather than the expected O(N/B). This vulnerability is a partial incomplete fix of the earlier CVE-2026-70453, which bounded the hash chain walk length (MAX_CHAIN_LEN) but left the per-byte strong-checksum computation unbounded. The fix (commit a7404a9) introduces two mitigations: (1) deduplication of false-alarm chain entries via last_false_sum2 tracking to prevent redundant memcmp calls, and (2) a consecutive_false_offsets counter that skips a full block window after 4 consecutive weak-checksum collisions without a strong-checksum match, bounding CPU work to O(N/B) (GitHub PR #1132, GitHub Commit).

Impact

Successful exploitation causes complete CPU exhaustion of the rsync sender process across concurrent connections, rendering the rsync daemon unavailable (denial of service). There is no confidentiality or integrity impact — the vulnerability is purely an availability issue. Public-facing rsync daemon modules are most at risk, as no authentication is required; an attacker can open multiple concurrent connections to amplify the CPU exhaustion effect and sustain service unavailability (GitHub PR #1132, Feedly).

Exploitability

A proof-of-concept exploit flow is documented in the GitHub Security Advisory (GHSA-hjxm-xmq9-74q9), which describes cloning rsync v3.5.1, extracting the regression test from the fix commit, and running it to reproduce the CPU-exhaustion behavior — though no standalone weaponized exploit script exists. There is no evidence of in-the-wild exploitation as of the time of publication. The vulnerability is automatable (no authentication or user interaction required), and the EPSS score is approximately 0.627%, indicating low but non-negligible exploitation probability. It has not been added to the CISA KEV catalog (GitHub Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify internet-facing rsync daemons with publicly accessible modules using tools like Shodan (search for port 873) or by probing with rsync rsync://<target>/ to list available modules. Confirm the target runs rsync ≤ 3.5.1 or ≤ 3.2.7.
  2. Craft colliding weak checksums: Construct a source file containing byte sequences whose Adler-32 rolling checksum (weak checksum) collides with the receiver's basis file block checksums at consecutive 1-byte offsets, but whose strong checksums (MD4/MD5/SHA1) do not match any basis block. Large even block sizes (e.g., 64 KiB or 128 KiB) make collisions easier due to modulo 65536 arithmetic in get_checksum1().
  3. Initiate rsync pull: Connect to the target daemon as an unauthenticated client pulling from a public module: rsync rsync://<target>/<module>/ /tmp/out/ --no-whole-file --block-size=131072
  4. Trigger CPU exhaustion: The crafted checksums cause the sender's hash_search() to compute a full strong checksum at every byte offset across the colliding region — O(N×B) work. Open multiple concurrent connections to amplify the effect and sustain CPU saturation.
  5. Sustain denial of service: Maintain concurrent connections to keep sender CPU pegged at 100%, preventing legitimate rsync operations from completing (GitHub PR #1132, GitHub Advisory).

Indicators of compromise

  • Network: Unusually high number of concurrent inbound connections on TCP port 873 (rsync daemon port) from one or few source IPs; connections that remain open for extended periods without completing a transfer.
  • Process: rsync sender process(es) consuming 100% CPU on one or more cores for sustained periods; top or ps showing multiple rsync processes in a CPU-bound state simultaneously.
  • Logs: rsync daemon logs (/var/log/rsyncd.log or syslog) showing repeated connections from the same client IP to a public module with large block sizes or unusual transfer patterns; abnormally high false_alarms counts in debug-level rsync output (--debug=deltasum1).
  • System: Load average spiking proportionally to the number of concurrent rsync connections; system responsiveness degradation correlated with rsync daemon activity.

Mitigation and workarounds

Upgrade rsync to version 3.5.2 (or 3.2.8 for systems on the 3.2.x LTS branch), which contain the fix introduced in commit a7404a9. For systems that cannot immediately upgrade, restrict access to rsync daemon modules to trusted IP ranges using the hosts allow directive in rsyncd.conf, or disable public anonymous module access entirely if not required. Rate-limiting concurrent connections to the rsync daemon (e.g., via firewall rules or the max connections parameter in rsyncd.conf) can reduce the impact of exploitation attempts (GitHub PR #1132, GitHub Commit, Microsoft MSRC).

Community reactions

The rsync maintainer (steadytao) initially questioned whether the issue warranted a CVE, noting it was not a memory corruption bug and only affected a single connection's sender CPU. However, contributor samueloph argued that since the earlier CVE-2026-70453 (which bounded the chain walk) was rated HIGH, this incomplete fix — leaving per-byte strong-checksum computation unbounded — warranted its own CVE for downstream distribution tracking. The fix was merged on October 20, 2026, and the CVE was published on November 3, 2026. Coverage appeared in security news outlets including Help Net Security and Linuxiac, noting the rsync 3.5.2 release. Slackware, Red Hat, Amazon Linux, Alpine Linux, and other distributions issued security advisories and updated packages (GitHub PR #1132, Help Net Security, Red Hat).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

rsync: 3.5.0+ds1-0+deb12u1

Fixed

sid

rsync: 3.5.2+ds1-1

Fixed

trixie

rsync: 3.5.0+ds1-0+deb13u2

Fixed

Ubuntu

Affected

bionic (esm-infra)

rsync

Unknown

devel

rsync: 3.5.2+ds1-2

Affected

focal (esm-infra)

rsync

Unknown

jammy

rsync

Unknown

noble

rsync

Unknown

resolute

rsync

Unknown

trusty (esm-infra-legacy)

rsync

Unknown

xenial (esm-infra-legacy)

rsync

Unknown

RHEL / CentOS

Fixed

OpenShift

openshift/ose-rhel-coreos-8

Affected

RHEL 8

:baseos:rsync-0:3.1.3-30.el8_10.src

Fixed

RHEL 9

:appstream:rsync-0:3.2.7-1.el9_8.2.src

Fixed

RHEL 10

rsync-0:3.5.0-3.el10_2.1.src

Fixed

Alpine

Fixed

edge

rsync: 3.5.2-r0

Fixed

v3.19

3.1.2-r7

Affected

v3.20

3.1.2-r7

Affected

v3.21

rsync: 3.5.2-r0

Fixed

v3.22

rsync: 3.5.2-r0

Fixed

v3.23

rsync: 3.5.2-r0

Fixed

v3.24

3.4.3-r1

Affected

Source: This report was generated using AI

Related rsync vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-119741HIGH8.7
  • rsync logorsync
  • net-misc/rsync
NoYesNov 03, 2026
CVE-2026-70464HIGH8.7
  • rsync logorsync
  • rsync-rrsync
NoYesAug 13, 2026
CVE-2026-70463HIGH8.6
  • rsync logorsync
  • cpe:2.3:a:google:cloud_sql_sqlserver
NoYesAug 13, 2026
CVE-2026-85091HIGH8.3
  • rsync logorsync
  • minizip-compat
NoYesSep 03, 2026
CVE-2026-18743LOW2.5
  • rsync logorsync
  • popt
NoYesSep 01, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management