CVE-2026-70456

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — Patch released this week
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

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 (value × EchelonGraph’s weight)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

September 8, 2026

Advisory Details (3)

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

rsync 3.0.1 < 3.5.0 Heap Out-of-Bounds Write via read_args() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-heap-out-of-bounds-write-via-read-args
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 advisoryMentions a patch (unverified)

rsync: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs · Advisory · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/security/advisories/GHSA-78jc-79jv-v6rw

Vendor Advisories for CVE-2026-70456(3)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcostmanagement/costmanagement-ui-rhel10:17914608512026-10-08redhat
redhatrsync-0:3.1.3-28.el8_102026-09-30redhat
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202609221802-02026-09-29redhat
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 rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.7-1 ... 3.5.1+ds1-1 (32 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (13 versions)
  • every version up to 3.5.0+ds1-0+deb13u1: fixed in 3.5.0+ds1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions)
  • every version up to 3.5.0+ds1-1: fixed in 3.5.0+ds1-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 13× in last 7d / 83× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 178 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-70456?
CVE-2026-70456 is a high-severity vulnerability; its CVE record was published on August 13, 2026. 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…
When was CVE-2026-70456 made public?
CVE-2026-70456 was made public on August 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-70456 actively exploited?
CVE-2026-70456 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70456?
CVE-2026-70456 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70456?
A fix for CVE-2026-70456 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70456 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-70456?

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

Book a Demo →Browse All CVEs