CVE-2026-101028

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:eef
Trending — 3 sources updated this weekElevated
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.0Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Incorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3.

Ash.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) applied only the root resource's read policy before running the aggregate query. The read path also applies each related resource's read policy to filter and sort references that cross a relationship, directly (for example comments.body) or through an aggregate over one, but the aggregate path skipped that step. A caller whose filter or sort reaches these functions, for example through Ash.Query.filter_input/2, an ash_lua script, or an AshAi tool offering count or exists results, can test conditions against related rows hidden from them and recover their existence and attribute values one query at a time. Ash.read/2 and its page counts are not affected.

This issue affects ash: from 2.6.0 before 3.34.6.

CVSS v3
6.0
EG Score
6.0MEDIUMlow confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 9, 2026

Last Modified

October 9, 2026

Advisory Details (5)

Auto-updated Oct 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-101028
githubMentions a patch (unverified)🟡 PoC Available

Ash.count, Ash.exists and Ash.aggregate skip related read policies in user filters · Advisory · ash-project/ash · GitHub

https://github.com/ash-project/ash/security/advisories/GHSA-xj24-8f5c-pp5p
github_commit Patch Available

commit 80936187b27e (ash-project/ash)

Patch available: ash-project/ash v3.34.6 (contains commit 80936187b27e)

https://github.com/ash-project/ash/commit/80936187b27ee94f15cd875affd3141b5cb23185
github_commit Patch Available

commit 30eaf1c6e852 (ash-project/ash)

Patch available: ash-project/ash v3.26.0 (contains commit 30eaf1c6e852)

https://github.com/ash-project/ash/commit/30eaf1c6e8524527b703e3c4bfeff7967ee0b37c

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-09 18:19 UTCEG score recompute
  3. 2026-10-09 07:27 UTCEG score recompute
  4. 2026-10-09 07:08 UTCEG score recompute
  5. 2026-10-09 07:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-101028?
CVE-2026-101028 is a medium vulnerability published on October 9, 2026. Incorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3. Ash.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) applied only the root resource's read policy before running the…
When was CVE-2026-101028 disclosed?
CVE-2026-101028 was first published on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101028 actively exploited?
CVE-2026-101028 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-101028?
CVE-2026-101028 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-101028?
A fix for CVE-2026-101028 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-101028

Explore →

Is Your Infrastructure Affected by CVE-2026-101028?

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