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%, top 68% 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, nvd
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.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.2(medium)
EG Risk
37(Track)
EG Risk 37/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

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
github Patch Available

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(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(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 23× in last 7d / 86× 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 105 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 68.4% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70457, 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-70457

Explore →

Is Your Infrastructure Affected by CVE-2026-70457?

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