Security readout for executives and security teams
Plain-English summary
Rsync versions 3.4.2 and earlier can mishandle file paths during certain filesystem operations. A local attacker who can modify files in an exported rsync module may race symlink changes to affect files outside that module when the daemon runs with 'use chroot = no'.
Executive priority
Treat as high priority where rsync modules are used with local write access and no chroot isolation. It is not described as remotely exploitable by unauthenticated network attackers in the provided sources.
Technical view
The issue is a symlink race in rsync path-based syscalls such as chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat. It maps to CWE-367 and CWE-59, has CVSS 4.0 score 7.2, and is fixed in rsync 3.4.3 per provided sources.
Likely exposure
Exposure is most likely on rsync daemons running 3.4.2 or earlier, with exported modules configured 'use chroot = no', where local users or processes can alter module filesystem contents.
Exploitation context
The provided sources describe local exploitation requiring low privileges, attacker filesystem access, and a timing race. KEV is false in the bundle, and no provided source establishes active exploitation.
Researcher notes
Focus triage on daemon mode, module boundaries, path-based operations, and local filesystem control. Evidence is limited to the supplied advisory metadata and references; do not assume broader affected products or exploitation beyond the provided rsync scope.
Mitigation direction
- Upgrade rsync to version 3.4.3 where supported.
- Prioritize daemons with exported modules using 'use chroot = no'.
- Restrict local write access to exported module paths.
- Review vendor advisory guidance for any environment-specific mitigations.
Validation and detection
- Inventory rsync daemon versions and flag 3.4.2 or earlier.
- Review rsync daemon module configuration for 'use chroot = no'.
- Identify local users or workloads able to modify exported module paths.
- Confirm rsync 3.4.3 is deployed and daemon services restarted.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-367: 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.
Open ATT&CK lookupCWE-59: 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.
Open ATT&CK lookupCVE-2026-43619 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N15.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.2HighVector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/RsyncProject/rsync/security/advisories/GHSA-4h9m-w5ff-j735CVE reference, VulnCheck · vendor-advisory
- https://github.com/RsyncProject/rsync/releases/tag/v3.4.3CVE reference, VulnCheck · release-notes
- https://www.vulncheck.com/advisories/rsync-symlink-race-condition-via-path-based-syscallsCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.