Vulnerability in github.com/rclone/rclone (CVE-2026-71310)
Summary
Vulnerability in github.com/rclone/rclone (CVE-2026-71310). Risk of unauthorized operations or information disclosure. Exploitable via http.ReadResponse. Mitigation: upgrade to 1.75.0 or later.
Original description
The description as published by the source.
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.0, the shared HTTP CONNECT helper in lib/proxy/http.go parses proxy CONNECT responses with http.ReadResponse over an unrestricted buffered reader, allowing a malicious or compromised configured proxy, or an active on-path actor controlling a plaintext HTTP proxy hop, to send oversized headers that grow memory until the rclone process fails. The affected helper is used by FTP and SFTP proxy connections, and SFTP reaches the parser before SSH server authentication, so target host key validation does not constrain a malicious proxy. This issue is fixed in 1.75.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-71310 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like http.ReadResponse over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade github.com/rclone/rclone to 1.75.0 or later.
If unsure, ask your IT team or search "github.com/rclone/rclone CVE-2026-71310" on the vendor's site.
CVE-2026-71310 (github.com/rclone/rclone) — CWE-400 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: http.ReadResponse / a0c09f1381ae93e2a9a33c529d170186c61ad058 / HTTPConnectDial / http.Transport.MaxResponseHeaderBytes
Patched: 1.75.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in github.com/rclone/rclone. Attackers reach the vulnerable code path via http.ReadResponse without authentication.
Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: http.ReadResponse / a0c09f1381ae93e2a9a33c529d170186c61ad058 / HTTPConnectDial / http.Transport.MaxResponseHeaderBytes.
Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.
Update to 1.75.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/rclone/rclone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/rclone/rclone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/rclone/rcloneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/rclone/rclone to 1.75.0ステージング環境で 1.75.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-71310 rclone
- Ubuntu UBUNTU-CVE-2026-71310 rclone
References
- web github.com
- web github.com
- web github.com
- web github.com
- web pkg.go.dev
- web nvd.nist.gov