CVE-2026-69160

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.5EG
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.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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.4%
EPSS %ILE
32nd
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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.

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

July 24, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

Arbitrary File Read via Path Prefix Confusion in Share Creation API · Advisory · OpenListTeam/OpenList · GitHub

https://github.com/OpenListTeam/OpenList/security/advisories/GHSA-86cx-wwf4-phq4
GitHub release Patch Available

v4.2.4

Patch available: OpenListTeam/OpenList v4.2.4

https://github.com/OpenListTeam/OpenList/releases/tag/v4.2.4
GitHub commit

commit 59bd34314085 (OpenListTeam/OpenList)

Fix landed in OpenListTeam/OpenList commit 59bd34314085 — awaiting tagged release

https://github.com/OpenListTeam/OpenList/commit/59bd3431408578f420895457554700cc9a52375a

Vendor Advisories for CVE-2026-69160(1)

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

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/OpenListTeam/OpenList—
  • every version on: no fix on record
—
github.com/OpenListTeam/OpenList/v3—
  • every version on: no fix on record
—
github.com/OpenListTeam/OpenList/v4—
  • every version up to 4.2.4: fixed in 4.2.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-18 03:19 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-12 15:44 UTCEG score recompute
  11. 2026-10-11 19:29 UTCEG score recompute
  12. 2026-10-11 16:45 UTCEG score recompute
  13. 2026-10-11 14:05 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-04 07:41 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-02 19:42 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 61 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-01 04:32 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-28 04:25 UTCEG score recompute
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-25 09:59 UTCEG score recompute
  9. 2026-09-23 22:16 UTCEG score recompute
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-22 22:09 UTCEG score recompute
  12. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-09-20 01:39 UTCEG score recompute
  15. 2026-09-18 20:35 UTCEG score recompute
  16. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-09-18 04:19 UTCEG score recompute
  18. 2026-09-17 05:29 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-09-16 06:38 UTCEG score recompute
  21. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-14 16:01 UTCEG score recompute
  23. 2026-09-12 15:29 UTCEG score recompute
  24. 2026-09-11 16:35 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-09-10 13:33 UTCEG score recompute
  28. 2026-09-09 08:43 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-09-07 21:23 UTCEG score recompute
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-06 18:28 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-09-05 19:22 UTCEG score recompute
  35. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-09-04 12:44 UTCEG score recompute
  37. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-09-01 23:15 UTCEG score recompute
  40. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-08-30 23:05 UTCEG score recompute
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-08-30 00:14 UTCEG score recompute
  46. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  47. 2026-08-27 11:02 UTCEG score recompute
  48. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-08-26 12:11 UTCEG score recompute
  50. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-08-24 14:29 UTCEG score recompute
  52. 2026-08-23 15:38 UTCEG score recompute
  53. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-08-22 16:47 UTCEG score recompute
  55. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  56. 2026-08-21 17:57 UTCEG score recompute
  57. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-08-19 20:17 UTCEG score recompute
  59. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  60. 2026-08-18 18:25 UTCEG score recompute
  61. 2026-08-18 18:08 UTCEG score recomputeFirst assessed: 6.5 MEDIUM

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-69160?
CVE-2026-69160 is a medium-severity vulnerability; its CVE record was published on July 24, 2026. OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a…
When was the CVE record for CVE-2026-69160 published?
The CVE record for CVE-2026-69160 was published on July 24, 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 18, 2026; the record at its source may have been updated since.
Is CVE-2026-69160 actively exploited?
CVE-2026-69160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69160?
CVE-2026-69160 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69160?
A fix for CVE-2026-69160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69160 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-69160

Explore →

Is Your Infrastructure Affected by CVE-2026-69160?

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

Book a Demo →Browse All CVEs