CVE-2026-70454 exposes a critical gap in rsync's TLS transport modes: certificate validation was not enforced, allowing trivial man-in-the-middle attacks against supposedly encrypted rsync sessions. The CVSS 8 rating is technically accurate for the vulnerability's impact, but the EPSS of 0.0019 reflects a narrower reality — this affects a code path (rsync's openssl mode and the rsync-ssl stunnel wrapper) that most production deployments have already abandoned in favor of SSH transport. That abandonment, however, is exactly what makes this worth your attention: organizations still running rsync-over-TLS likely did so specifically because they believed TLS provided MITM protection equivalent to SSH. The CVSS score assumes a reasonable user expectation that the software failed to meet — but there's a deeper question that changes how you should prioritize this: was the missing validation ever a deliberate design choice rather than an oversight? The openssl mode in rsync has been effectively unmaintained since approximately rsync 3.2.0, and if the maintainers intentionally shipped it as a minimal encryption wrapper expecting users to handle authentication out-of-band, this CVE formalizes a gap between what the ecosystem assumed TLS mode provided and what the software was ever designed to deliver. The stunnel wrapper failure in rsync-ssl is a distinct vulnerability class — if rsync-ssl invokes stunnel without explicitly setting verification flags, it creates an invisible integration failure where safe defaults get silently overridden. Regardless of whether this was regression, design gap, or documentation failure, your remediation path is straightforward: audit any rsync-over-TLS workflows in your environment, migrate those workloads to SSH transport if possible, or if TLS is required, explicitly configure certificate validation in your stunnel configuration with verifyChain = yes or equivalent. The CVSS 8 will trigger compliance and scanning attention, but the actual exploitation surface is narrower than the severity score implies.
CVE-2026-70454
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedrsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe application does not properly validate the TLS certificate presented by the other side — skipping the chain, the hostname, or expiry — so an attacker with a forged or mismatched certificate can sit in the middle of a supposedly secure connection. It is a common trap in custom clients and misconfigured libraries. The fix is full certificate validation, and never disabling verification to make errors go away.
General guidance for the improper certificate validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedrsync 3.2.4+ (openssl mode) or rsync-ssl 3.4.5+ (stunnel mode)
- 1. Identify the exact rsync version currently installed by running 'rsync --version'
- 2. For openssl mode: upgrade rsync to version 3.2.4 or later which contains the fix for certificate validation
- 3. For stunnel mode: upgrade rsync-ssl to version 3.4.5 or later which contains the fix
- 4. After upgrading, verify the new version is installed: 'rsync --version'
- 5. Test rsync connections to ensure functionality is maintained
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-70454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-70454 exposes a critical gap in rsync's TLS transport modes: certificate validation was not enforced, allowing trivial man-in-the-middle attacks against supposedly encrypted rsync sessions. The CVSS 8 rating is technically accurate for the vulnerability's impact, but the EPSS of 0.0019 reflects a narrower reality — this affects a code path (rsync's openssl mode and the rsync-ssl stunnel wrapper) that most production deployments have already abandoned in favor of SSH transport. That abandonment, however, is exactly what makes this worth your attention: organizations still running rsync-over-TLS likely did so specifically because they believed TLS provided MITM protection equivalent to SSH. The CVSS score assumes a reasonable user expectation that the software failed to meet — but there's a deeper question that changes how you should prioritize this: was the missing validation ever a deliberate design choice rather than an oversight? The openssl mode in rsync has been effectively unmaintained since approximately rsync 3.2.0, and if the maintainers intentionally shipped it as a minimal encryption wrapper expecting users to handle authentication out-of-band, this CVE formalizes a gap between what the ecosystem assumed TLS mode provided and what the software was ever designed to deliver. The stunnel wrapper failure in rsync-ssl is a distinct vulnerability class — if rsync-ssl invokes stunnel without explicitly setting verification flags, it creates an invisible integration failure where safe defaults get silently overridden. Regardless of whether this was regression, design gap, or documentation failure, your remediation path is straightforward: audit any rsync-over-TLS workflows in your environment, migrate those workloads to SSH transport if possible, or if TLS is required, explicitly configure certificate validation in your stunnel configuration with `verifyChain = yes` or equivalent. The CVSS 8 will trigger compliance and scanning attention, but the actual exploitation surface is narrower than the severity score implies.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-70454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data