Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.45% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-70462High confidence
rsync 3.1.0 < 3.5.0 Signed Integer Overflow via MSG_IO_TIMEOUT
RsyncProject · rsync
Official source article: GitHub GHSA-J9WH-5JMP-2M64 ↗. Check the applicable product and release in the original source.
7.1HighCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs RsyncProject rsync and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 15 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
8 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | rsync | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.5.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | rsync | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.5.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | rsync | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.5.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | rsync | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.5.0+ds1-0+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | rsync | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | rsync | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.5.0+ds1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | rsync | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.5.0+ds1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | rsync | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-70462 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-70462
The vendor explicitly identifies these products as affected by this CVE.
- rsync as component of SUSE Linux Enterprise High Performance Computing 12 SP5
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- rsync as component of SUSE Linux Enterprise Server 12 SP5-LTSS
- rsync as component of SUSE Linux Enterprise Server 12 SP5
- rsync as component of SUSE Linux Enterprise Server 15 SP1-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP1
- rsync as component of SUSE Linux Enterprise Server 15 SP2-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP2
- rsync as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP3
- Summary
- rsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-70462 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityrsync: rsync: Denial of Service via signed integer overflow in I/O timeout
The vendor explicitly identifies these products as affected by this CVE.
- rsync as a component of Red Hat Enterprise Linux 10
- rsync-daemon as a component of Red Hat Enterprise Linux 10
- rsync-rrsync as a component of Red Hat Enterprise Linux 10
- rsync.src as a component of Red Hat Enterprise Linux 10
- rsync as a component of Red Hat Enterprise Linux 7
- rsync.src as a component of Red Hat Enterprise Linux 7
- rsync as a component of Red Hat Enterprise Linux 8
- rsync-daemon as a component of Red Hat Enterprise Linux 8
- rsync.src as a component of Red Hat Enterprise Linux 8
- rsync as a component of Red Hat Enterprise Linux 9
- rsync-daemon as a component of Red Hat Enterprise Linux 9
- rsync-rrsync as a component of Red Hat Enterprise Linux 9
- Summary
- A flaw was found in rsync. A remote attacker can exploit a signed integer overflow vulnerability in the I/O timeout implementation by sending specially crafted messages. These messages can disable connection timeouts, causing idle or stalled connections to persist indefinitely. This leads to resource exhaustion, preventing legitimate users from accessing the rsync service and resulting in a denial of service.
- Remediation
- Only run rsync against trusted remotes. Restrict which hosts local rsync and rsync-bpc may reach. A peer MSG_IO_TIMEOUT can disable or overflow the client’s --timeout; daemon hosts allow does not bind this.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
rsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.
What
rsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.
Why
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.
What
rsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.
Why
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Integer Overflow or Wraparound → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Passive interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-190 ↗
CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- rsync as component of SUSE Linux Enterprise High Performance Computing 12 SP5
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- rsync as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- rsync as component of SUSE Linux Enterprise Server 12 SP5-LTSS
- rsync as component of SUSE Linux Enterprise Server 12 SP5
- rsync as component of SUSE Linux Enterprise Server 15 SP1-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP1
- rsync as component of SUSE Linux Enterprise Server 15 SP2-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP2
- rsync as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- rsync as component of SUSE Linux Enterprise Server 15 SP3
- rsync as component of SUSE Linux Enterprise Server LTSS Extended Security 12 SP5
- rsync as component of SUSE Linux Enterprise Server Teradata 12 SP3
- rsync as component of SUSE Linux Enterprise Server for SAP Applications 12 SP5
- rsync as component of SUSE Linux Enterprise Server for SAP Applications 15 SP1
- rsync as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2
- rsync as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3
- SLES 15 SP1 CHOST Images for Amazon EC2
- SLES 15 SP2 CHOST Images for Amazon EC2
- SLES 15 SP3 CHOST Images for Amazon EC2
- SLES 15 SP4 CHOST Images for Amazon EC2
- SLES 15 SP5 CHOST Images for Amazon EC2
- SLES 15 SP1 CHOST Images for Google
- SLES 15 SP2 CHOST Images for Google
- SLES 15 SP3 CHOST Images for Google
- SLES 15 SP4 CHOST Images for Google
- SLES 15 SP5 CHOST Images for Google
- SLES 15 SP1 CHOST Images for Microsoft Azure
- SLES 15 SP2 CHOST Images for Microsoft Azure
- and 3 more
- Fixed
- rsync: 3.5.0
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 13 Aug 2026 · Last source change 14 Aug 2026, 16:51 UTC · CWE-190 · Integer Overflow or Wraparound
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-58042
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
- After
- rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4
- After
- rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-70462 to remediation: access.redhat.com/CVE-2026-70462.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-70462
- After
- remediation: access.redhat.com/CVE-2026-70462
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- After
- rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.