Rsync is a file-copying tool that uses a delta-transfer algorithm to synchronize remote and local files. In versions prior to 3.4.3, the receiver's compressed-token decoder accumulated a 32-bit signed counter without checking for overflow. A malicious sender can trigger an overflow that with careful manipulation can lead to the extraction of data stored in memory of the process allowing an attacker to access environment variables, passwords and memory pointers from the heap, stack, and libraries. The leakage of these pointers and data can significantly reduce the effectiveness of ASLR and facilitate further exploitation. This issue is fixed in version 3.4.3.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-44508 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-43618. Reason: This candidate is a duplicate of CVE-2026-43618. Notes: All CVE users should reference CVE-2026-43618 instead of this candidate.
CVE-2026-44508
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 20, 2026
Advisory Details (1)
Auto-updated Jul 20, 2026rsync: Integer overflow in compressed-token decoding enables remote memory dump · Advisory · RsyncProject/rsync · GitHub
Affected: 3.4.3
https://github.com/RsyncProject/rsync/security/advisories/GHSA-g37v-g3gj-pmwqVendor Advisories for CVE-2026-44508(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 0× in last 7d / 1× 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.
- 2026-08-01 14:00 UTCEG score recompute
- 2026-07-26 10:46 UTCEG score recompute
- 2026-07-23 03:15 UTCEG score recompute▼ 8.10
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 22:42 UTCEG score recompute
- 2026-07-20 20:52 UTCEG score recompute
- 2026-07-20 20:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-200
Frequently asked(5)
What is CVE-2026-44508?
When was CVE-2026-44508 disclosed?
Is CVE-2026-44508 actively exploited?
What is the CVSS score of CVE-2026-44508?
How do I remediate CVE-2026-44508?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44508
Is Your Infrastructure Affected by CVE-2026-44508?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.