rclone denial of service in RC JSON request handling
Affects rclone 1.46.0 up to before 1.76.0 when the remote control (RC) server runs without HTTP authentication. Fixed in 1.76.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.76.0
- Who is exposed
- Specific setups only
Summary
Written by a model
Rclone from 1.46.0 before 1.76.0 contains a memory exhaustion vulnerability in the remote control server that allows unauthenticated clients to crash rclone by sending oversized JSON bodies. Attackers can POST large JSON payloads to protected RC methods, which handlePost decodes before authorization checks, triggering out-of-memory termination and interrupting transfers.
Who should check
Teams running rclone 1.46.0 through 1.75.2 with the RC server enabled without HTTP authentication, especially hosts with limited memory running rcd.
Not fixed by: Loopback binding is not an OS-user isolation boundary; local users can still reach RC.
“When rclone's remote control (RC) server is enabled without HTTP authentication”
What to do
Check whether your setup matches what the bug needs.
rclone remote control (RC) server is enabled without HTTP authentication Affected rclone versions are 1.46.0 up to before 1.76.0 A service memory budget is limited (the demonstrated OOM needs a finite memory limit)Upgrade to a fixed version: 1.76.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134349 (Rclone from 1.46.0 before 1.76.0 Denial of Service via RC JSON Requests), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134349 (entry last updated 2026-11-21):
Affected:
- rclone rclone: from 1.46.0, fixed in 1.76.0
Fixed versions: 1.76.0.
Conditions (all must be true for the bug to be hit):
- rclone remote control (RC) server is enabled without HTTP authentication (source: https://github.com/rclone/rclone/security/advisories/GHSA-f8p4-8g4j-q3m2)
- Affected rclone versions are 1.46.0 up to before 1.76.0 (source: https://www.vulncheck.com/advisories/rclone-from-1.46.0-before-1.76.0-denial-of-service-via-rc-json-requests)
- A service memory budget is limited (the demonstrated OOM needs a finite memory limit) (source: https://github.com/rclone/rclone/security/advisories/GHSA-f8p4-8g4j-q3m2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-134349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134349 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/rclone/rclone/security/advisories/GHSA-f8p4-8g4j-q3m2
- https://www.vulncheck.com/advisories/rclone-from-1.46.0-before-1.76.0-denial-of-service-via-rc-json-requests
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134349
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134349"}.Affected versions
- rclone rcloneFrom 1.46.0 · fixed in 1.76.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · rclone/rclone · Advisory GHSA-f8p4-8g4j-q3m2 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134349 |
| Record | NVD · CVE-2026-134349 |
| Other links 1 | |
| Link | vulncheck.com · advisories/rclone-from-1.46.0-before-1.76.0-denial-of-service-via-rc-json-requests |
Questions about CVE-2026-134349
Is CVE-2026-134349 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A party that can reach the rclone remote control (RC) server without HTTP authentication can crash a memory-constrained rclone process. That interrupts active transfers and other services running in the same process, which is a denial of service.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-134349?
rclone: from 1.46.0 before 1.76.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 1.46.0 up to before 1.76.0 are affected. The issue needs the RC server enabled without HTTP authentication and a finite memory limit on the service. To check, run rclone version for the installed version and review whether the RC server is enabled and whether HTTP authentication is configured.
Source: github.com, vulncheck.com
How do I fix CVE-2026-134349?
Upgrade to rclone 1.76.0, the fixed version listed for this vulnerability.
Source: github.com, vulncheck.com
Why do the sources disagree?
The description says the attack works against RC without HTTP authentication, while the CVSS vector lists privileges required as Low (PR:L), which implies some access is needed first. The CVSS score is 6.8 (medium). No vendor severity rating is provided, so the sources do not give a separate vendor view.
Source: github.com, vulncheck.com
Related
- CVE-2026-134352Rclone 1.51.0 before 1.76.0 Authentication Bypass via serve sftp Auth-Proxy Cache
- CVE-2026-116191Rclone before 1.75.2 Path Traversal via serve webdav MKCOL
- CVE-2026-116192rclone from 1.37 before 1.74.2 SSRF via --rc-serve scheme-relative remote roots
- CVE-2026-116189rclone 1.55.0 before 1.75.2 selfupdate Signature Verification Bypass via SHA256SUMS
- CVE-2026-116194Rclone 1.52.0 before 1.75.2 CSRF via pCloud OAuth Callback
- CVE-2026-88045rclone: S3 multipart declared-length memory exhaustion
No corrections so far. Something wrong on this page? Report an error.