CVE-2026-70458

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
Patch available. Sources: github_release, github.
generic

rsync 3.0.0 < 3.5.0 Out-of-Bounds Write via FLAG_HLINKED Handling | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-out-of-bounds-write-via-flag-hlinked-handling
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
github Patch Available

rsync: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H · Advisory · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/security/advisories/GHSA-gg3m-4m9m-268h

Vendor Advisories for CVE-2026-70458(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrsync-0:3.5.0-3.el10_22026-09-14redhat
redhatrsync-0:3.2.7-1.el9_82026-09-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
rsync3.5.0-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync3.5.0-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync3.5.0-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync3.5.0-r0
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1 ... 3.5.0+ds1-2 (30 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.5.0+ds1-2 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions)3.5.0+ds1-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 23× in last 7d / 94× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 114 total refreshes for this CVE.

  1. 2026-09-19 00:59 UTCEG score recompute
  2. 2026-09-19 00:59 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 12:50 UTCVendor advisory
  5. 2026-09-18 00:29 UTCEG score recompute
  6. 2026-09-18 00:29 UTCVendor advisory
  7. 2026-09-17 12:04 UTCVendor advisory
  8. 2026-09-17 00:00 UTCEG score recompute
  9. 2026-09-17 00:00 UTCVendor advisory
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-16 02:48 UTCVendor advisory
  13. 2026-09-15 14:44 UTCEG score recompute
  14. 2026-09-15 14:44 UTCVendor advisory
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 14:20 UTCVendor advisory
  17. 2026-09-14 02:12 UTCEG score recompute
  18. 2026-09-14 02:12 UTCVendor advisory
  19. 2026-09-13 14:09 UTCVendor advisory
  20. 2026-09-13 02:06 UTCEG score recompute
  21. 2026-09-13 02:06 UTCVendor advisory
  22. 2026-09-12 15:02 UTCEPSS rescore
  23. 2026-09-12 14:01 UTCVendor advisory
  24. 2026-09-12 01:57 UTCEG score recompute
  25. 2026-09-12 01:57 UTCVendor advisory
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 13:53 UTCEG score recompute
  3. 2026-09-10 13:44 UTCEG score recompute
  4. 2026-09-10 09:35 UTCEPSS rescore
  5. 2026-09-09 08:59 UTCEG score recompute
  6. 2026-09-09 08:59 UTCVendor advisory
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-08 20:55 UTCEG score recompute
  9. 2026-09-08 06:25 UTCVendor advisory
  10. 2026-09-07 17:49 UTCEG score recompute
  11. 2026-09-07 17:49 UTCVendor advisory
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-07 05:44 UTCEG score recompute
  14. 2026-09-07 05:44 UTCVendor advisory
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 13:43 UTCVendor advisory
  17. 2026-09-06 01:39 UTCEG score recompute
  18. 2026-09-06 01:39 UTCVendor advisory
  19. 2026-09-05 15:31 UTCEPSS rescore
  20. 2026-09-05 13:35 UTCVendor advisory
  21. 2026-09-05 01:24 UTCEG score recompute
  22. 2026-09-05 01:24 UTCVendor advisory
  23. 2026-09-04 13:11 UTCEG score recompute
  24. 2026-09-04 13:11 UTCVendor advisory
  25. 2026-09-04 05:07 UTCEPSS rescore
  26. 2026-09-04 01:01 UTCVendor advisory
  27. 2026-09-03 11:17 UTCVendor advisory
  28. 2026-09-02 23:11 UTCEG score recompute
  29. 2026-09-02 23:11 UTCVendor advisory
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-01 23:25 UTCEG score recompute
  32. 2026-09-01 23:25 UTCVendor advisory
  33. 2026-09-01 13:54 UTCEPSS rescore
  34. 2026-09-01 11:21 UTCEG score recompute
  35. 2026-09-01 11:21 UTCVendor advisory
  36. 2026-09-01 04:40 UTCEPSS rescore
  37. 2026-08-31 21:51 UTCVendor advisory
  38. 2026-08-31 09:48 UTCVendor advisory
  39. 2026-08-30 20:35 UTCEG score recompute
  40. 2026-08-30 20:35 UTCVendor advisory
  41. 2026-08-30 19:17 UTCEPSS rescore
  42. 2026-08-30 08:31 UTCEG score recompute
  43. 2026-08-30 08:31 UTCVendor advisory
  44. 2026-08-30 01:22 UTCEPSS rescore
  45. 2026-08-29 20:27 UTCVendor advisory
  46. 2026-08-29 07:40 UTCEG score recompute
  47. 2026-08-29 07:40 UTCVendor advisory
  48. 2026-08-28 21:42 UTCEPSS rescore
  49. 2026-08-28 09:03 UTCVendor advisory
  50. 2026-08-27 20:59 UTCEG score recompute
  51. 2026-08-27 20:59 UTCVendor advisory
  52. 2026-08-27 08:56 UTCVendor advisory
  53. 2026-08-26 20:52 UTCEG score recompute
  54. 2026-08-26 20:52 UTCVendor advisory
  55. 2026-08-26 14:47 UTCEPSS rescore
  56. 2026-08-26 08:44 UTCVendor advisory
  57. 2026-08-25 20:40 UTCEG score recompute
  58. 2026-08-25 20:40 UTCVendor advisory
  59. 2026-08-25 13:49 UTCEPSS rescore
  60. 2026-08-25 08:26 UTCVendor advisory
  61. 2026-08-24 20:04 UTCEG score recompute
  62. 2026-08-24 20:04 UTCVendor advisory
  63. 2026-08-24 08:00 UTCVendor advisory
  64. 2026-08-23 07:52 UTCEG score recompute
  65. 2026-08-23 00:19 UTCEPSS rescore
  66. 2026-08-22 07:45 UTCEG score recompute
  67. 2026-08-21 23:49 UTCEPSS rescore
  68. 2026-08-21 07:38 UTCEG score recompute
  69. 2026-08-20 22:56 UTCEPSS rescore
  70. 2026-08-19 19:27 UTCEG score recompute
  71. 2026-08-19 17:04 UTCEPSS rescore
  72. 2026-08-18 19:20 UTCEG score recompute
  73. 2026-08-18 13:49 UTCEPSS rescore
  74. 2026-08-18 13:49 UTCEPSS rescore
  75. 2026-08-17 19:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-70458?
CVE-2026-70458 is a high vulnerability published on August 13, 2026. rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINKBUMP processing on file entries with the FLAGHLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing FSUM field in the…
When was CVE-2026-70458 disclosed?
CVE-2026-70458 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70458 actively exploited?
CVE-2026-70458 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.4% of all scored CVEs.
What is the CVSS score of CVE-2026-70458?
CVE-2026-70458 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-70458?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70458, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70458

Explore →

Is Your Infrastructure Affected by CVE-2026-70458?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.