CVE-2026-78216

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. 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: epss, secondary
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

AshLua exposes Ash read actions to Lua scripts run through an eval action. A read call accepts an operation (list, min, max, first, sum, avg) that builds an ad-hoc Ash.Query.Aggregate over a named field and returns its raw value.

Ash field policies redact forbidden fields on returned records (replacing them with %Ash.ForbiddenField{}), but that redaction does not apply to aggregate values. A script could therefore read a field the calling actor's field policies forbid by requesting it as an aggregate instead of as a field. This includes fields that are public? true but restricted per-actor by a field policy, such as sensitive PII. The prior hardening only enforced the exposed-field allow-list (field visibility), which is a separate axis from per-actor field-policy authorization.

The fix authorizes the aggregated field against the resource's field policies, so aggregating over a field the actor may not see is refused or scoped to the rows where it is visible.

This issue affects ash_lua: from 0.1.0 before 0.2.2.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Sep 8, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 266a5dcc56d5 (ash-project/ash_lua)

Patch available: ash-project/ash_lua v0.2.2 (contains commit 266a5dcc56d5)

https://github.com/ash-project/ash_lua/commit/266a5dcc56d5015b6d316c10606169e753b07450
github_commit Patch Available

commit 8675e47cca81 (ash-project/ash_lua)

Patch available: ash-project/ash_lua v0.1.0 (contains commit 8675e47cca81)

https://github.com/ash-project/ash_lua/commit/8675e47cca81f36594083a7e63379bac9e123e72
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-78216
generic

CVE-2026-78216

https://cna.erlef.org/cves/CVE-2026-78216.html
github Patch Available

AshLua eval read operations can read field-policy-protected fields via aggregates · Advisory · ash-project/ash_lua · GitHub

https://github.com/ash-project/ash_lua/security/advisories/GHSA-5whv-8rcp-x33j

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_lua0.1.0 ... 0.2.1 (9 versions)0.2.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 20× 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-09-19 06:20 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:32 UTCEG score recompute
  4. 2026-09-17 04:44 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 03:55 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 02:18 UTCEG score recompute
  11. 2026-09-13 01:30 UTCEG score recompute
  12. 2026-09-12 00:42 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 23:54 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 19:48 UTCEG score recompute
  18. 2026-09-08 18:13 UTCEG score recompute
  19. 2026-09-08 16:51 UTCEG score recompute
  20. 2026-09-08 16:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78216?
CVE-2026-78216 is a medium vulnerability published on September 8, 2026. AshLua exposes Ash read actions to Lua scripts run through an eval action. A read call accepts an operation (list, min, max, first, sum, avg) that builds an ad-hoc Ash.Query.Aggregate over a named field and returns its raw value. Ash field policies redact forbidden fields on returned records…
When was CVE-2026-78216 disclosed?
CVE-2026-78216 was first published in the National Vulnerability Database on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78216 actively exploited?
CVE-2026-78216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.8% of all scored CVEs.
What is the CVSS score of CVE-2026-78216?
CVE-2026-78216 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-78216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78216, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78216?

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

Start Free Scan →Browse All CVEs