CVE-2026-45232

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

Rsync versions before 3.4.3 contain an off-by-one out-of-bounds stack write vulnerability in the establish_proxy_connection() function in socket.c that allows network attackers to corrupt stack memory by sending a malformed HTTP proxy response. Attackers can exploit this by positioning themselves between the client and proxy or controlling the proxy server to send a response line of 1023 or more bytes without a newline terminator, causing a null byte to be written to an out-of-bounds stack address when the RSYNC_PROXY environment variable is set.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

References (3)

Vendor Advisories for CVE-2026-45232(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
ubuntursync (3.1.1-3ubuntu1.3+esm5) @ xenial2026-08-24ubuntu
ubuntursync (3.4.1+ds1-7ubuntu0.2) @ resolute2026-08-24ubuntu

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync—3.4.3-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.3-4 ... 3.4.4+ds1-1 (39 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1 ... 3.2.7-1+deb12u5 (6 versions)3.2.7-1+deb12u6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5, 3.4.1+ds1-5+deb13u1, 3.4.1+ds1-5+deb13u2, 3.4.1+ds1-5+deb13u33.4.1+ds1-5+deb13u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.4.2+ds1-2 (6 versions)3.4.3+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 5× in last 7d / 29× 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 156 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45232?
CVE-2026-45232 is a low vulnerability published on May 20, 2026. Rsync versions before 3.4.3 contain an off-by-one out-of-bounds stack write vulnerability in the establishproxyconnection() function in socket.c that allows network attackers to corrupt stack memory by sending a malformed HTTP proxy response. Attackers can exploit this by positioning themselves…
When was CVE-2026-45232 disclosed?
CVE-2026-45232 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45232 actively exploited?
CVE-2026-45232 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 72.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45232?
CVE-2026-45232 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-45232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45232, 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-45232

Explore →

Is Your Infrastructure Affected by CVE-2026-45232?

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

Start Free Scan →Browse All CVEs