Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to public anonymous rsync daemon module
-
DeliveryInitiate pull as malicious receiver
-
ExploitSupply colliding weak checksums with non-matching strong checksums
-
ExecutionForce unbounded strong-checksum work in hash_search()
-
ImpactExhaust sender CPU across concurrent connections
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Algorithmic complexity limits
|
| Exploitation Conditions | Exploitation requires the target to run rsync in daemon mode (rsyncd) exposing a public or anonymous module that permits pull/download transfers, with the attacker acting as the receiving peer in the delta-transfer protocol; the attacker then crafts weak-checksum collisions at consecutive rolling-window offsets paired with non-matching strong checksums to trigger the O(N) strong-checksum walk in hash_search(). Limiting factors: default rsync usage as an SSH-invoked client or one-off command does not expose this vector - only a configured, reachable public daemon module does - and impact is confined to CPU/availability exhaustion (no confidentiality or integrity loss). Authentication is not required per the CVSS vector (PR:N), but a non-default public-daemon deployment is a hard prerequisite. |
| Impact | This is a genuine but bounded operational risk rather than a top-tier emergency. The CVSS 4.0 signals (AV:N/AC:L/AT:N/PR:N/UI:N, score 8.7) describe a remote, low-complexity, unauthenticated path with high availability impact and zero confidentiality or integrity impact (VC:N/VI:N/VA:H) - consistent with CWE-407 (inefficient algorithmic complexity / algorithmic-complexity DoS). The vuln.today decision label is 'this_week', not act_now or emergency, which aligns with a resource-exhaustion DoS that is serious for exposed daemons but not a code-execution or data-exposure flaw. No EPSS score is provided and the vulnerability is NOT in CISA KEV, so there is no evidence of active or widespread exploitation; it was reported by VulnCheck with a vendor patch already available. The input marks no confirmed public exploit, though the upstream fix (PR #1132) ships a regression test (hashsearch-collision-skip_test.py) that concretely demonstrates the collision-flood technique, lowering the bar for weaponization. The key real-world qualifier not captured by the network CVSS vector: exploitation requires the target to run rsync as a daemon exposing a public/anonymous module that permits pulls - a non-default deployment. So while the raw score is high, actual exposure is limited to internet-facing or shared rsync daemon servers; hosts using rsync only as an ad-hoc SSH client are not reachable via this vector. |
| Exploit ScenarioDerived | An attacker connects to an internet-facing rsync daemon offering a public, anonymous, pullable module and initiates a file transfer as the receiver. During delta transfer the attacker supplies weak (rolling) checksums that collide at consecutive offsets together with non-matching strong checksums, forcing the sender's hash_search() in match.c into unbounded per-byte strong-checksum computation and exhausting server CPU across concurrent connections. No authentication or user interaction is required (PR:N/UI:N), though no confirmed working exploit is published - only an upstream regression test that demonstrates the collision pattern. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Remote CPU exhaustion in rsync's delta-transfer sender lets a malicious receiving peer starve a public rsync daemon module of processing capacity. The flaw affects rsync builds through 3.5.1 when exposed through rsyncd with a module that permits anonymous or public pull/download transfers; the attacker supplies weak checksums that collide at consecutive rolling-window offsets while the paired strong checksums do not match, forcing hash_search() in match.c into a per-byte strong-checksum walk instead of the normal per-block stride, and parallel connections compound the load. Impact is availability-only (CVSS 4.0 8.7, VC:N/VI:N/VA:H; independently assessed CVSS 3.1 8.7 AV:N/AC:L/PR:N/UI:N/A:H), no public exploit code exists at time of analysis, and the hard prerequisite is a non-default public daemon deployment - rsync invoked over SSH as a client is not exposed.
RemediationAI
Apply the upstream fix referenced by the CVE: PR https://github.com/RsyncProject/rsync/pull/1132, commit https://github.com/RsyncProject/rsync/commit/a7404a9a633cff28ee1602f328b9c3fa69cdbd04 (patch status: available from vendor), and track https://github.com/RsyncProject/rsync for the tagged release that carries it, since a released patched version number is not independently confirmed in the provided data - downstream packagers should verify their shipped build includes this commit rather than assuming. Because exploitation requires the receiving peer role against a reachable daemon module, the strongest interim control is to eliminate that exposure: stop advertising anonymous/public modules and require authentication (auth users plus secrets file) on any module reachable from untrusted networks, with the trade-off that unauthenticated mirroring and public distribution points stop working for existing consumers. Where public read access must remain, restrict who can reach the module via hosts allow/hosts deny in rsyncd.conf and firewall rules limiting the rsync port (873/tcp) to known client networks, accepting that this reduces the service's reachability for legitimate anonymous users. Additionally, prefer rsync over SSH or an authenticated transport instead of running rsyncd on untrusted interfaces, and cap concurrency (max connections plus OS-level connection rate limiting) so that even a successful flood cannot consume all sender CPU - noting that these rate limits only reduce the amplification and do not remove the underlying per-connection cost. Refer to the VulnCheck advisory and the project regression test referenced above for details on validating the collision bounding after the fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
rsync's delta-transfer algorithm breaks the basis file into blocks whose checksums are computed by the receiver and sent to the sender. Each block carries a weak rolling checksum (sum1) and a strong checksum (sum2), and hash_search() in match.c rolls a window across the sender's file, probing a hash table keyed on the weak checksum and only confirming a match with the strong checksum. Because the weak checksum is deliberately cheap and collision-prone, the code anticipates false alarms - weak hits that fail the strong comparison - but it historically assumed they would be rare and isolated. CVE-2026-119741 is a CWE-407 inefficient-algorithm-complexity defect: a crafted block whose weak checksum collides across a long run of consecutive rolling-window offsets, paired with strong checksums that never match, converts that assumption into O(N) strong-checksum computations per file instead of roughly O(N / block length), and every concurrent receiving connection adds another such walk. The supplied upstream fix (PR #1132, commit a7404a9a633cff28ee1602f328b9c3fa69cdbd04) adds a counter of consecutive false offsets that skips ahead once four in a row occur, deduplicates chain entries that share an identical last-false strong checksum, and moves the block-length comparison ahead of the chain traversal. The accompanying testsuite/hashsearch-collision-skip_test.py regression test documents both the CPU bounding (hash_hits/false_alarms bounded at O(N / blength)) and exact boundary-match preservation across skip points, including --inplace mode.
Know when Rsync gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Unauthenticated network-reachable receiver triggers low-complexity algorithmic DoS against a public daemon; availability-only impact, no confidentiality or integrity effect, no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
rsync through 3.5.1 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.
Executive ViewAI
A high-severity availability flaw in rsync (CVE-2026-119741) allows an unauthenticated remote peer to exhaust CPU on public rsync daemon modules, degrading or halting download services for all legitimate users. Only organizations running rsync in daemon mode with anonymous or public pull modules are exposed; standard rsync-over-SSH client usage is not affected. Leadership should prioritize this wherever rsync underpins public file distribution, mirroring, or backup ingestion, as sustained service disruption could interrupt dependent operations.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
A flaw was found in rsync which could be triggered when rsync compares file checksums. Rated high severity (CVSS 7.5), t
A heap-based buffer overflow flaw was found in the rsync daemon. Rated critical severity (CVSS 9.8), this vulnerability
rsync 3.1.1 allows remote attackers to write to arbitrary files via a symlink attack on a file in the synchronization pa
Server-to-client path traversal in rsync lets a malicious or compromised rsync server write files outside the client's i
An issue was discovered in rsync before 3.2.5 that allows malicious remote servers to write arbitrary files inside the d
The check_secret function in authenticate.c in rsync 3.1.0 and earlier allows remote attackers to cause a denial of serv
A flaw was found in rsync. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authenticati
The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character
The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon_
rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to by
Arbitrary command execution in rsync before 3.5.0 arises from multiple unsanitized code paths - the RSYNC_CONNECT_PROG e
Arbitrary file write in rsync 2.3.3 through 3.4.4 lets a malicious sender escape a daemon module's root by abusing symli
EUVD-2026-115914
NVD
CVE.org
Vulnrichment
GitHub
Exploit-DB