# CVE-2026-70456: rsync 3.0.1 < 3.5.0 Heap Out-of-Bounds Write via read_args()

> A malicious sender can trigger a heap out-of-bounds write in rsync via crafted arguments, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** ALPINE-CVE-2026-70456, AZL-95843, BELL-CVE-2026-70456, CLSA-2026-1789569255, CLSA-2026-1789569581, CLSA-2026-1789579460, CLSA-2026-1789579702, CLSA-2026-1789580327, CLSA-2026-1789580939, CLSA-2026-1789745757, DEBIAN-CVE-2026-70456, ECHO-d2f4-19ef-8603, GHSA-78jc-79jv-v6rw, ROOT-OS-DEBIAN-11-CVE-2026-70456, UBUNTU-CVE-2026-70456

## What is CVE-2026-70456?

CVE-2026-70456 is a high-severity memory corruption vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-70456 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70456 is a high-severity memory corruption vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70456 in the wild and no public exploit code.

Affected product: RsyncProject 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-70456/ (Markdown: https://insights.sbomify.com/CVE-2026-70456/index.md)
```

## Sources

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

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