CVE-2026-43618: Rsync < 3.4.3 Integer Overflow Information Disclosure
Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receiver process to read and return data from outside the intended buffer bounds. Attackers can exploit this vulnerability to disclose process memory contents including environment variables, passwords, heap and stack data, and library memory pointers, significantly reducing ASLR effectiveness and facilitating further exploitation.
Security readout for executives and security teams
Plain-English summary
Rsync 3.4.2 and earlier can leak memory from a receiving rsync process when processing malicious compressed transfer data. Leaked memory may include secrets, environment variables, stack or heap data, and pointers that weaken ASLR. Treat exposed rsync workflows involving untrusted senders as urgent.
Executive priority
Prioritize remediation for externally reachable or partner-facing rsync services. Memory disclosure can expose operational secrets and make later compromise easier, even though active exploitation is not confirmed in the supplied evidence.
Technical view
The issue is an integer overflow in rsync's compressed-token decoder. An unchecked 32-bit signed counter can wrap, causing the receiver to read and return data outside intended buffer bounds. Sources map this to CWE-125 and CWE-190 with CVSS 8.1, confidentiality high and availability high.
Likely exposure
Likely exposure is rsync 3.4.2 or earlier where a receiver processes sender-controlled transfer data. Internet-facing rsync services, backup pipelines, mirrors, and automation accepting low-privileged or external senders deserve priority review.
Exploitation context
The bundle marks KEV as false, and the provided sources do not establish active exploitation. The described attack requires a malicious sender able to interact with a vulnerable receiver; no weaponized exploit details are needed to assess risk.
Researcher notes
Evidence supports an out-of-bounds read caused by integer overflow in compressed-token decoding. The source bundle does not provide proof-of-concept status, detailed affected platform matrices beyond rsync 3.4.2 and earlier, or non-rsync product impact.
Mitigation direction
Upgrade rsync to version 3.4.3 where available.
Apply relevant vendor backport updates, including applicable Red Hat errata.
Restrict rsync access to trusted senders until patched.
Review vendor guidance for distribution-specific fixed package versions.
Reduce exposure of public rsync services where business permits.
Validation and detection
Inventory rsync versions across servers, containers, appliances, and backup hosts.
Identify rsync receivers processing data from external or low-privileged senders.
Confirm fixed package status against vendor advisories or rsync 3.4.3 release notes.
Review recent rsync service logs for unexpected sender activity.
Verify remediation through package metadata, not only upstream version strings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
3CVSS vectors
5Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
3 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.