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-side out-of-bounds array read in rsync's recv_files() lets a malicious rsync server (or any peer acting in the sender role) deterministically crash any rsync client that pulls from it. The trigger is fully wire-protocol-level, requires no special options on the victim, and works for both rsync:// URLs and remote-shell pulls; since inc_recurse is the protocol-30+ default, any client doing a normal recursive pull against an attacker-controlled URL is exposed. A malicious server sets CF_INC_RECURSE, sends a flist whose first sorted entry is not the leading "." directory (causing parent_ndx to be set to -1), then sends a transfer record with ndx = 0 and an iflag omitting ITEM_TRANSFER, causing the receiver to read 8 bytes before the allocated pointer array and dereference the result in f_name(). The impact is crash-only: the out-of-bounds read lands in glibc mmap chunk metadata and dereferences to an unmapped low address, producing a SEGV that cannot be leveraged into an exploit (confirmed on glibc x86-64 Linux; non-glibc allocators not audited). This issue is fixed in version 3.4.3.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-44510 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-43620. Reason: This candidate is a duplicate of CVE-2026-43620. Notes: All CVE users should reference CVE-2026-43620 instead of this candidate.
CVE-2026-44510
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 0.0(none)
- EG Risk
- 0EG Risk 0/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. It is distinct from the 0–10 EG Score, which measures severity.
- EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 20, 2026
Advisory Details (1)
Auto-updated Jul 20, 2026rsync: receiver-side out-of-bounds read enables remote DoS from malicious server · Advisory · RsyncProject/rsync · GitHub
https://github.com/RsyncProject/rsync/security/advisories/GHSA-28pw-r563-rxvmVendor Advisories for CVE-2026-44510(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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-07-26 10:45 UTCEG score recompute
- 2026-07-23 03:15 UTCEG score recompute▼ 6.50
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 22:42 UTCEG score recompute
- 2026-07-20 21:23 UTCEG score recompute
- 2026-07-20 21:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125
Frequently asked(5)
What is CVE-2026-44510?
When was CVE-2026-44510 disclosed?
Is CVE-2026-44510 actively exploited?
What is the CVSS score of CVE-2026-44510?
How do I remediate CVE-2026-44510?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44510
Is Your Infrastructure Affected by CVE-2026-44510?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.