CVE-2026-88015

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-09-10. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-75575 (ENISA EUVD) · GHSA-p6m2-r3w9-mpxw (GitHub Security Advisories) · GO-2026-6461 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%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. Prior to 1.75.1, backend/local with --links or links=true exposes symlink targets as .rclonelink objects, and fs.RangeOption.Decode can pass an unchecked positive Range start through Object.Open and openTranslatedLink. The function slices the target string as linkdst[offset:], so a Range start larger than the target length causes a deterministic slice-bounds panic when lib/http/serve exposes the object through HTTP or WebDAV. Go net/http normally recovers the panic per connection, causing request-level denial of service rather than terminating the entire process. This issue is fixed in version 1.75.1.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
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.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 (3)

Auto-updated Sep 10, 2026
Patch available. Sources: github, github_commit, github_release.
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 28bf49d66f94 (rclone/rclone)

Fix landed in rclone/rclone commit 28bf49d66f94 — awaiting tagged release

https://github.com/rclone/rclone/commit/28bf49d66f94acc3f4f7f318504a706686281af9
GitHub advisoryMentions a patch (unverified)

local: crafted Range request against a translated symlink panics (DoS), sibling of the already-fixed #6310 · Advisory · rclone/rclone · GitHub

https://github.com/rclone/rclone/security/advisories/GHSA-p6m2-r3w9-mpxw

Vendor Advisories for CVE-2026-88015(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.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—
  • every version up to 1.75.1: fixed in 1.75.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 91 is merged into the row it repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-p6m2-r3w9-mpxw · GitHub severity MODERATE · GitHub CVSS 5.3
  3. 2026-11-01 07:37 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-29 22:55 UTCOSV refresh
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-25 13:53 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-22 12:34 UTCEG score recompute
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-18 03:03 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 65 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  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.4% · 27th percentile
  7. 2026-10-11 13:49 UTCEG score recompute
  8. 2026-10-11 10:13 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-10 09:06 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-09 08:24 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-10-08 07:43 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-07 07:01 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-06 06:18 UTCEG score recompute
  19. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-05 05:31 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-10-04 04:49 UTCEG score recompute
  23. 2026-10-03 04:09 UTCEG score recompute
  24. 2026-10-02 03:28 UTCEG score recompute
  25. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  26. 2026-10-01 02:37 UTCEG score recompute
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  28. 2026-09-30 01:56 UTCEG score recompute
  29. 2026-09-29 01:01 UTCEG score recompute
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-28 00:20 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-26 23:39 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-24 21:46 UTCEG score recompute
  36. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-09-23 20:48 UTCEG score recompute
  38. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-23 04:18 UTCEG score recompute
  40. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-09-22 03:38 UTCEG score recompute
  42. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-09-21 02:57 UTCEG score recompute
  44. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  45. 2026-09-20 02:16 UTCEG score recompute
  46. 2026-09-19 01:35 UTCEG score recompute
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-09-18 00:55 UTCEG score recompute
  49. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  50. 2026-09-17 00:14 UTCEG score recompute
  51. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  52. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-09-15 23:33 UTCEG score recompute
  54. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  55. 2026-09-13 22:11 UTCEG score recompute
  56. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  57. 2026-09-12 21:29 UTCEG score recompute
  58. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  59. 2026-09-11 20:48 UTCEG score recompute
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  61. 2026-09-10 19:59 UTCEG score recompute
  62. 2026-09-10 16:20 UTCEG score recompute
  63. 2026-09-10 16:10 UTCEG score recompute
  64. 2026-09-10 15:55 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  65. 2026-09-10 15:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88015?
CVE-2026-88015 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. Prior to 1.75.1, backend/local with --links or links=true exposes symlink targets as .rclonelink objects, and fs.RangeOption.Decode can pass an unchecked positive Range start through…
When was the CVE record for CVE-2026-88015 published?
The CVE record for CVE-2026-88015 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-88015 actively exploited?
CVE-2026-88015 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88015?
CVE-2026-88015 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88015?
A fix for CVE-2026-88015 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88015 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-88015

Explore →

Is Your Infrastructure Affected by CVE-2026-88015?

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