LiveActive security incident?Get immediate response
CVE Record

CVE-2026-53790: rsync < 3.5.0 Command Injection via Multiple Code Paths

rsync before 3.5.0 contains multiple command and argument injection vulnerabilities that allow attackers to execute arbitrary commands by supplying malicious input through several code paths, including the RSYNC_CONNECT_PROG environment variable, daemon hooks, the rsync-ssl wrapper, and remote-shell command newline injection. Attackers can inject shell metacharacters or newline characters into unsanitized user-supplied values such as hostnames and hostspecs to execute arbitrary commands under the privileges of the rsync process or the invoking user.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Rsync versions before 3.5.0 can treat malicious connection details as commands. If attacker-controlled hostnames, host specifications, or related settings reach vulnerable paths, arbitrary commands may run with the rsync process or invoking user’s privileges, risking data theft, alteration, and service disruption.

Executive priority

Begin urgent inventory and remediation. Prioritize exposed or privileged automation because successful exploitation could compromise confidentiality, integrity, and availability. The absence of KEV listing does not remove risk, but active exploitation is not established by the supplied evidence.

Technical view

Multiple CWE-78 and CWE-88 flaws affect command construction in RSYNC_CONNECT_PROG, daemon hooks, the rsync-ssl wrapper, and remote-shell handling. Unsanitized shell metacharacters or newline characters in hostnames and hostspecs can cause command execution. The supplied CVSS 4.0 score is 9.2, with network reachability but high attack complexity.

Likely exposure

Exposure is highest where rsync before 3.5.0 processes untrusted hostnames or hostspecs, uses daemon hooks or rsync-ssl, or permits attacker influence over RSYNC_CONNECT_PROG. Actual reachability depends on deployment configuration, input provenance, and rsync process privileges.

Exploitation context

The supplied record indicates network attackability without authentication or user interaction, but high attack complexity. It is not listed in KEV, and the supplied sources provide no evidence of active exploitation. Treat proof-of-concept availability and observed attacks as unconfirmed.

Researcher notes

The issue spans several command-building boundaries rather than one isolated parser. Validation should map which vulnerable paths are reachable and whether attacker-controlled values cross into them. The supplied version statement says versions before 3.5.0 are affected; precise downstream package status requires distributor confirmation.

Mitigation direction

  • Upgrade affected rsync installations to version 3.5.0 or later using trusted vendor packages.
  • Prioritize internet-facing, automated, privileged, daemon-mode, and rsync-ssl deployments.
  • Prevent untrusted users or upstream systems from controlling hostnames, hostspecs, hooks, or RSYNC_CONNECT_PROG.
  • Restrict rsync execution privileges and review vendor guidance for deployment-specific mitigations.

Validation and detection

  • Inventory rsync versions across servers, appliances, containers, backup systems, and automation runners.
  • Identify workflows where external input influences hostnames, hostspecs, daemon hooks, rsync-ssl, or RSYNC_CONNECT_PROG.
  • Confirm upgraded systems report rsync 3.5.0 or later from their trusted package source.
  • Review rsync execution identities and investigate unexpected child processes or command activity.
  • Retest affected workflows after remediation without using malicious payloads in production.
Prepared
Confidence
high
Sources
5

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 · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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 lookup
cwe · medium confidence lookup

CWE-88: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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 lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-53790 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 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.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NVulnCheck
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-53790Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RsyncProjectrsync0, 3.5.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.