# CVE-2026-119741: rsync < 3.5.2 Denial of Service via hash_search() Checksum Collisions


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** ALPINE-CVE-2026-119741, AZL-112646, BELL-CVE-2026-119741, DEBIAN-CVE-2026-119741, ECHO-c4a8-6894-2dcd, GHSA-56w4-j8c7-xvrw, UBUNTU-CVE-2026-119741, openSUSE-SU-2026:12443-1

## What is CVE-2026-119741?

CVE-2026-119741 is a high-severity vulnerability in Rsync, published on 3 Nov 2026. 

### Official description

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.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

## Which versions are affected by CVE-2026-119741?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync` | openSUSE:Tumbleweed | All versions | 3.5.2-1.1 |

Products: Rsync.

## How do I fix CVE-2026-119741?

Upgrade to a fixed version.

## Is CVE-2026-119741 being exploited?

There is no known exploitation of CVE-2026-119741 in the wild and no public exploit code.

## Other vulnerabilities in Rsync

- [CVE-2017-15994](https://insights.sbomify.com/CVE-2017-15994/): rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access restrictions. (critical 9.8)
- [CVE-2026-53790](https://insights.sbomify.com/CVE-2026-53790/): rsync < 3.5.0 Command Injection via Multiple Code Paths (critical 9.2)
- [CVE-2026-70460](https://insights.sbomify.com/CVE-2026-70460/): rsync 2.3.3 < 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (critical 9.2)
- [CVE-2026-53791](https://insights.sbomify.com/CVE-2026-53791/): rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (critical 9.1)
- [CVE-2026-53793](https://insights.sbomify.com/CVE-2026-53793/): rsync < 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119741 and fix it if it is affected.

What it is: CVE-2026-119741 is a high-severity vulnerability in Rsync, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119741 in the wild and no public exploit code.

Affected product: Rsync. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119741/ (Markdown: https://insights.sbomify.com/CVE-2026-119741/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119741
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119741
- OSV: https://osv.dev/vulnerability/CVE-2026-119741

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119741/
Summaries are generated and may contain mistakes; the official description above is the record.