CVE-2026-102663

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (17th 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

Also known asEUVD-2026-97775 (ENISA EUVD) · GO-2026-6113 (OSV.dev)Source: ENISA EUVD

4.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.3%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenList is a file list program that supports multiple storage backends. Prior to 4.2.4, the OpenList search API uses a non-separator-aware strings.HasPrefix comparison as a path containment authorization check when authorizing globally indexed Bleve results against a restricted user's BasePath. When Bleve search is enabled and a restricted authenticated user searches the global index for content in a sibling path, the user causes a globally indexed sibling-path result to pass the prefix check. The strings.HasPrefix(node.Parent, user.BasePath) predicate allows a sibling path such as /base2 to be treated as contained by /base. Unauthorized file metadata or file-existence information can be disclosed, and the backend Total value can reveal a match even when another access check removes the individual result. This issue is fixed in version 4.2.4.

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

EG Severity
4.3 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.3% within 30 daysSource: FIRST EPSS. 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

October 12, 2026

Last Modified

October 13, 2026

Advisory Details (4)

Auto-updated Oct 13, 2026
Patch available. Sources: github, github_commit, github_release.
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 84ecda35aae2 (OpenListTeam/OpenList)

Fix landed in OpenListTeam/OpenList commit 84ecda35aae2 — awaiting tagged release

https://github.com/OpenListTeam/OpenList/commit/84ecda35aae2bd0020474086e6ddfd3aa2340679
GitHub commit

commit 59bd34314085 (OpenListTeam/OpenList)

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

https://github.com/OpenListTeam/OpenList/commit/59bd3431408578f420895457554700cc9a52375a
GitHub advisoryMentions a patch (unverified)

OpenList Bleve search authorization bypass via non-separator-aware BasePath validation · Advisory · OpenListTeam/OpenList · GitHub

https://github.com/OpenListTeam/OpenList/security/advisories/GHSA-p6ph-3jx2-3337

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(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-27 11:55 UTCOSV refresh
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-18 05:10 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-13 17:29 UTCEG score recompute
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 5 more
  1. 2026-10-13 16:32 UTCEG score recompute
  2. 2026-10-13 16:24 UTCEG score recompute
  3. 2026-10-12 19:26 UTCEG score recompute
  4. 2026-10-12 18:57 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  5. 2026-10-12 18:55 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102663?
CVE-2026-102663 is a medium-severity vulnerability; its CVE record was published on October 12, 2026. OpenList is a file list program that supports multiple storage backends. Prior to 4.2.4, the OpenList search API uses a non-separator-aware strings.HasPrefix comparison as a path containment authorization check when authorizing globally indexed Bleve results against a restricted user's BasePath.…
When was the CVE record for CVE-2026-102663 published?
The CVE record for CVE-2026-102663 was published on October 12, 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 October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-102663 actively exploited?
CVE-2026-102663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102663?
CVE-2026-102663 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102663?
A fix for CVE-2026-102663 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102663?

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

Book a Demo →Browse All CVEs