CVE-2026-70457

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). 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, nvd
Trending — 3 sources updated 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.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

rsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

August 31, 2026

Advisory Details (3)

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

rsync 3.2.3 < 3.5.0 Out-of-Bounds Write via parse_size_arg() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-out-of-bounds-write-via-parse-size-arg
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
githubMentions a patch (unverified)

rsync: Attacker-chosen-offset write in parse_size_arg() error formatting · Advisory · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/security/advisories/GHSA-pg7g-xqmr-xpfh

Vendor Advisories for CVE-2026-70457(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhcos-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—
  • 3.2.3 up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.2.3 up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.2.3 up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • 3.2.3 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(2)

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 17× in last 7d / 84× 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 161 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-70457?
CVE-2026-70457 is a high vulnerability published on August 13, 2026. rsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parsesizearg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that…
When was CVE-2026-70457 disclosed?
CVE-2026-70457 was first published on August 13, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70457 actively exploited?
CVE-2026-70457 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70457?
CVE-2026-70457 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-70457?
A fix for CVE-2026-70457 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70457 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-70457

Explore →

Is Your Infrastructure Affected by CVE-2026-70457?

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

Book a Demo →Browse All CVEs