CVE-2026-88013

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-10) is not newer than that change (2026-09-23), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-75567 (ENISA EUVD) · GHSA-486v-q2wf-fp2r (GitHub Security Advisories) · GO-2026-6463 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.49.0 until 1.75.1, the HTTP backend attaches headers configured through --http-headers or headers= to requests in backend/http/http.go, while its fshttp.NewClient client follows redirects without a backend-specific http.Client.CheckRedirect policy. A configured remote that redirects to another host can therefore cause custom secrets such as X-Api-Key to be resent to that untrusted destination, and a same-host HTTPS-to-HTTP redirect can expose Authorization or Cookie headers in cleartext. Listing, stat, download, mount, and serve operations can trigger the leak during normal use. This issue is fixed in version 1.75.1.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2026

Last Modified

September 23, 2026

Advisory Details (5)

Auto-updated Sep 23, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

http backend forwards custom/auth headers to a different host on redirect · Advisory · rclone/rclone · GitHub

https://github.com/rclone/rclone/security/advisories/GHSA-486v-q2wf-fp2r
GitHub release Patch Available

rclone v1.75.1

Patch available: rclone/rclone v1.75.1

https://github.com/rclone/rclone/releases/tag/v1.75.1
GitHub commit

commit 925fb4fb21eb (rclone/rclone)

Fix landed in rclone/rclone commit 925fb4fb21eb — awaiting tagged release

https://github.com/rclone/rclone/commit/925fb4fb21eb25e75cd1b64fdd17ded857784bfc
GitHub commit

commit 79fbc0842f74 (rclone/rclone)

Fix landed in rclone/rclone commit 79fbc0842f74 — awaiting tagged release

https://github.com/rclone/rclone/commit/79fbc0842f74e02cb84f0e3e7261d169983c8831
GitHub commit

commit 22859b7e696c (rclone/rclone)

Fix landed in rclone/rclone commit 22859b7e696c — awaiting tagged release

https://github.com/rclone/rclone/commit/22859b7e696cea3c563c6ba04c6b7f91f74456b4

Vendor Advisories for CVE-2026-88013(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/rclone/rclone @ 1.75.1 (fixes >= 1.49.0, <= 1.75.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rclone1.60.1+dfsg-2 ... 1.69.3+dfsg-3 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rclone1.60.1+dfsg-4 ... 1.69.3+dfsg-3 (6 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/rclone/rclone—
  • 1.49.0 up to 1.75.1: fixed in 1.75.1
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 82 is merged into the row it repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-486v-q2wf-fp2r · GitHub severity LOW · GitHub CVSS 3.7
  3. 2026-11-01 07:37 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-27 10:25 UTCOSV refresh
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-25 13:53 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 03:03 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 56 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:13 UTCEG score recompute
  3. 2026-10-12 14:49 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:32 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-11 13:49 UTCEG score recompute
  8. 2026-10-10 23:18 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-09 23:11 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-08 23:47 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-06 23:18 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-05 23:55 UTCEG score recompute
  18. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-04 23:41 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-04 00:17 UTCEG score recompute
  22. 2026-10-03 00:34 UTCEG score recompute
  23. 2026-10-02 01:10 UTCEG score recompute
  24. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-01 01:20 UTCEG score recompute
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-09-30 01:56 UTCEG score recompute
  28. 2026-09-28 20:21 UTCEG score recompute
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  30. 2026-09-27 20:14 UTCEG score recompute
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-09-26 20:50 UTCEG score recompute
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  34. 2026-09-24 20:06 UTCEG score recompute
  35. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  36. 2026-09-23 20:42 UTCEG score recompute▲ 1.60
  37. 2026-09-23 20:42 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  38. 2026-09-23 19:41 UTCEG score recompute
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-09-20 13:44 UTCEG score recompute
  44. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-09-17 07:49 UTCEG score recompute
  47. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-09-14 01:54 UTCEG score recompute
  51. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-09-10 16:20 UTCEG score recompute
  55. 2026-09-10 15:45 UTCEG score recomputeFirst assessed: 3.7 LOW
  56. 2026-09-10 15:44 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-88013?
CVE-2026-88013 is a medium-severity vulnerability; its CVE record was published on September 10, 2026. rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.49.0 until 1.75.1, the HTTP backend attaches headers configured through --http-headers or headers= to requests in backend/http/http.go, while its fshttp.NewClient client follows…
When was the CVE record for CVE-2026-88013 published?
The CVE record for CVE-2026-88013 was published on September 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-88013 actively exploited?
CVE-2026-88013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88013?
CVE-2026-88013 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-88013?
A fix for CVE-2026-88013 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88013 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88013

Explore →

Is Your Infrastructure Affected by CVE-2026-88013?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs