Skip to main content

rclone EUVDEUVD-2026-109450

| CVE-2026-116192 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-25 VulnCheck GHSA-j48m-mpf8-5cpg
8.2
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach unauthenticated --rc-serve RC listener
  2. Delivery
    Request existing named http/netstorage remote
  3. Exploit
    Supply scheme-relative '//host/path' root to bypass gate
  4. Execution
    Backend ResolveReference substitutes attacker authority
  5. Impact
    HEAD/GET to attacker host leaks body, headers, or NetStorage signature

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

All of the following non-default conditions must hold: (1) rclone rcd --rc-serve is enabled (default off); (2) the RC listener is reachable by the attacker (default bind is loopback only); (3) no RC HTTP authentication is configured; (4) --rc-no-auth is NOT set (this concerns the intermediate gated state, not the fully-open mode); (5) an http or netstorage named remote already exists in the config and the attacker knows or guesses its name. Custom-header disclosure additionally requires that the HTTP remote has configured headers. For HTTPS remotes the attacker endpoint must complete a TLS handshake with a certificate rclone trusts before headers are sent, unless --no-check-certificate is set. These factors sharply limit real-world exposure despite the network attack vector; only read-style HEAD/GET primitives are demonstrated, with no write capability.

Impact

This is a genuine but conditional SSRF (CWE-918) with associated credential/header exposure (CWE-522). The input supplies only a CVSS 4.0 vector (8.2: AV:N/AC:H/AT:P/PR:N/UI:N/VC:H) and the vuln.today priority 'this_week'; no EPSS score and no CISA KEV status are provided, so widespread or confirmed active exploitation cannot be asserted. The signals are internally consistent rather than conflicting: PR:N reflects that the named-remote gate is reached pre-auth, while AC:H and AT:P correctly capture that exploitation needs a specific non-default deployment (the GHSA author independently recommends CVSS 3.1 5.9 with AC:H, noting the same impact at AC:L would score 7.5). The real-world priority is therefore moderate and deployment-gated, not a drop-everything emergency: impact is confidentiality-only (HEAD/GET response disclosure, custom-header leakage, and NetStorage signing-oracle behavior) with no demonstrated write or integrity/availability impact. One data point warrants caution - the NVD/package metadata states fixed in 1.74.2 and affected <=1.74.1, yet the advisory body reports the behavior was still confirmed on v1.75.1 and present on current master, framing this as an incomplete-fix follow-up to CVE-2026-49980; verify the actual fixed build with the rclone maintainers.

Exploit ScenarioDerived

An operator runs rclone rcd --rc-serve reachable beyond loopback with no RC HTTP authentication and an existing http or netstorage remote configured. A remote attacker who knows (or guesses) that remote's name requests it with a scheme-relative //attacker-host:port/path root, which passes the named-remote gate but causes the backend to resolve the attacker's authority, returning the response body and leaking the remote's configured custom headers or a valid NetStorage request signature. A harmless loopback reproduction (Python PoC scripts using synthetic credentials) is included in the GHSA advisory, demonstrating the behavior but not verified as a weaponized exploit against production endpoints.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 25, 2026

Server-side request forgery in rclone's read-only RC file server (--rc-serve) lets unauthenticated users who can reach an exposed RC listener redirect http and netstorage backend requests to attacker-chosen hosts by supplying a root that begins with a double slash on an existing named remote. Successful requests return the target's response body to the requester, leak the named HTTP remote's configured custom headers to the selected host, and - for netstorage remotes - yield valid, time-bound request signatures for attacker-chosen stat and download paths. Exploitation requires a non-default deployment (--rc-serve enabled, listener reachable, no RC HTTP authentication, a known http or netstorage remote name), which is why the supplied assessment scores it CVSS:3.1 5.9 with AC:H despite the 8.2 CVSS 4.0 vector; there is no CISA KEV entry, and the advisory publishes loopback mock reproduction scripts that demonstrate synthetic-credential impact only, so no confirmed exploitation in the wild is indicated.

RemediationAI

Upgrade rclone to 1.74.2 or later, the version listed as fixed in the package metadata, and confirm against the vendor advisory at https://github.com/rclone/rclone/security/advisories/GHSA-xqmq-v4wj-rw5m; because the reporter observed the vulnerable joins still present in v1.75.1 and public master, re-test the double-slash root case on the exact binary you deploy before treating the issue as closed. Where upgrading is not immediately possible, remove the preconditions the flaw depends on: do not run rclone rcd --rc-serve on any listener an untrusted network can reach - keep the RC bind on loopback (the default) or firewall the RC port - and, if remote RC access is genuinely required, configure RC HTTP authentication so the named-remote gate is no longer the only control, while leaving in mind that setting --rc-no-auth removes all RC-function authentication and makes exposure strictly worse. Disabling --rc-serve entirely (it is off by default) eliminates the file-serving route and therefore this SSRF, at the cost of the read-only object browsing feature. Do not enable --no-check-certificate on http or netstorage remotes, since that removes the TLS trust requirement that currently limits header disclosure to attacker endpoints holding a certificate rclone trusts. Treat headers configured on http remotes and NetStorage secrets as potentially exposed if the RC listener was ever reachable without authentication, and rotate them. The upstream discussion recommends a same-origin/origin check around the URLJoin(base, URLPathEscape(root)) construction; until such a fix ships in your release, the deployment controls above are the practical containment.

Affected VersionsENISA

rclone 1.37 <1.74.2

Affected Packages

euvd rclone fix: 1.74.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a CWE-918 server-side request forgery whose root cause sits in URL construction shared by rclone's http and netstorage backends, with a secondary CWE-522 credential/secret exposure component when configured headers or NetStorage signatures reach the attacker's host. rclone's RC server gate in fs/rc/rcserver/rcserver.go intentionally allows unauthenticated --rc-serve access to remotes that already exist in the config while rejecting inline remotes, connection-string overrides and bare local paths; a root such as //host/path parses via fspath.Parse as an ordinary root on an existing named remote (Name set, Config empty), so it passes that gate. The backends then pass the root through lib/rest's URLPathEscape and URLJoin (base.ResolveReference), and because URLPathEscape preserves the leading double slash, Go parses the value as an RFC 3986 network-path reference, so ResolveReference replaces the configured URL authority before the first request. In the http backend, getFsEndpoint builds a HEAD for the substituted URL and addHeaders attaches the remote's configured custom headers before sending, so those headers are disclosed to the attacker's host; the redirect policy runs only after that first request is already constructed. In the netstorage backend the same join sets endpointURL before the signer is installed, and generateSignHeader covers auth data, RequestURI and action but not the host, which turns the affected instance into a time-bound signing oracle for stat and download requests reached through the file-serving route. Only same-scheme HEAD/GET primitives were demonstrated, with no write capability; on HTTPS remotes the attacker endpoint must present a certificate rclone trusts before headers are sent, unless --no-check-certificate is set. The reporter states the joins were confirmed on v1.75.1 and remain in public master without an origin check, and links the issue to prior work around CVE-2026-49980 / GHSA-qw24-gh76-8rvv and GHSA-486v-q2wf-fp2r.

Know when Rclone gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.2 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.9 MEDIUM

PR:N because the named-remote gate is reached pre-auth with no RC auth configured; AC:H for the required non-default reachable --rc-serve deployment; C:H for body/header/signature disclosure, no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Red Hat 5.9 MEDIUM

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 25, 2026 - 14:01 EUVD
CVE Published
Oct 25, 2026 - 13:20 cve.org
HIGH 8.2

DescriptionCVE.org

rclone from 1.37 before 1.74.2 contains a server-side request forgery vulnerability that allows unauthenticated attackers to redirect http and netstorage backend requests by supplying a double-slash root on an existing named remote via --rc-serve. Attackers can make HEAD/GET requests to attacker-chosen hosts to read responses, capture configured custom headers, or obtain valid NetStorage request signatures.

Technical POC Analysis

CWE-918 (SSRF); the advisory also tags CWE-522 because configured HTTP headers and NetStorage HMAC signatures leak.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity server-side request forgery vulnerability in rclone (CVE-2026-116192) affects organizations that have enabled the read-only RC file server without authentication. If exploited, unauthenticated attackers who can reach the exposed RC listener could redirect backend requests to attacker-controlled hosts, potentially leaking sensitive HTTP headers and enabling unauthorized data access. While exploitation requires a non-standard configuration, the impact on confidentiality and integrity could be significant for affected deployments.

Business Impact: High
Compensating Controls

Disable --rc-serve, enforce RC HTTP authentication, and restrict network access to the RC listener.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
High
rclone is a very widely deployed cloud/object-storage sync tool in DevOps and backup pipelines
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

More in Rclone

View all
CVE-2026-88018 CRITICAL POC
9.8 Sep 10

Authentication bypass in rclone's S3 server mode (rclone serve s3) allows any unauthenticated network attacker to impers

CVE-2026-71312 HIGH POC
8.0 Aug 05

PowerShell smart-quote filename injection in rclone's SFTP backend allows an attacker who controls remote filenames to e

CVE-2020-28924 HIGH POC
7.5 Nov 19

An issue was discovered in Rclone before 1.53.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploita

CVE-2026-88017 HIGH POC
7.3 Sep 10

Cross-session credential isolation failure in rclone's FTP auth-proxy driver (versions 1.64.0-1.75.0) allows an authenti

CVE-2026-88016 HIGH POC
7.1 Sep 10

Symlink escape in rclone's local backend (prior to v1.75.1) allows an attacker who controls sync source contents to appl

CVE-2026-71311 MEDIUM POC
6.4 Aug 05

FTP CRLF injection in rclone before 1.75.0 allows an attacker who can place crafted filenames in a source namespace to i

CVE-2026-88014 MEDIUM POC
6.3 Sep 10

Path traversal (Zip Slip class) in rclone's archive ZIP backend permits arbitrary file writes outside the intended desti

CVE-2026-88015 MEDIUM POC
5.3 Sep 10

Denial of service in rclone prior to 1.75.1 allows unauthenticated remote attackers to crash individual HTTP or WebDAV c

CVE-2026-88046 MEDIUM POC
5.3 Sep 10

Path traversal in rclone prior to 1.75.1 allows an attacker who can populate a source object store with raw `..` key seg

CVE-2026-79782 CRITICAL
9.3 Aug 25

Cleartext disclosure of AWS STS session tokens affects rclone before 1.74.4 when its S3 backend follows a redirect that

CVE-2026-88044 CRITICAL POC
9.1 Sep 10

Authentication/authorization bypass in rclone's dynamic serve interface (versions 1.70.0 through 1.75.0) lets remote att

CVE-2026-59733 HIGH POC
8.8 Jul 14

Path traversal in the `rclone serve restic --private-repos` REST server (versions prior to 1.74.4) allows an authenticat

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy