CVE-2026-82747

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

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

Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor.

When a resource has an access_type :runtime read policy (a check evaluated per record rather than compiled to a filter), Ash.Policy.Authorizer decides each record in check_result/1 (lib/ash/policy/authorizer/authorizer.ex) by discarding impossible policy scenarios and inspecting what remains. When every scenario for a record was impossible, meaning no policy can authorize it and it must be forbidden, the empty-scenario branch instead kept the record ({[record | data], authorizer, any_forbidden?}) and returned it as authorized. As a result, records the runtime read policy denies are returned to any actor. The fix forbids a record whose scenarios are all impossible.

This issue affects ash: from 3.4.44 before 3.32.2.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 1, 2026

Advisory Details (4)

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

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-82747
github Patch Available🟡 PoC Available

Incorrect authorization in `Ash.Policy.Authorizer` in Ash returns records denied by a runtime read policy to any actor · Advisory · ash-project/ash · GitHub

https://github.com/ash-project/ash/security/advisories/GHSA-4259-gvr2-4xhq
github_commit Patch Available

commit 6eddb8ab26e4 (ash-project/ash)

Patch available: ash-project/ash v3.32.2 (contains commit 6eddb8ab26e4)

https://github.com/ash-project/ash/commit/6eddb8ab26e45023faf0c79ebd152bb40aefda02

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash3.10.0 ... 3.9.0 (153 versions)3.32.2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 30× 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 10:45 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 06:01 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-16 03:35 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 23:04 UTCEG score recompute
  10. 2026-09-12 20:48 UTCEG score recompute
  11. 2026-09-11 18:33 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 16:17 UTCEG score recompute
  15. 2026-09-09 13:46 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 11:01 UTCEG score recompute
  18. 2026-09-07 08:43 UTCEG score recompute
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 04:11 UTCEG score recompute
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 23:37 UTCEG score recompute
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 21:21 UTCEG score recompute
  25. 2026-09-01 13:54 UTCEPSS rescore
Show 5 more
  1. 2026-09-01 13:42 UTCEG score recompute
  2. 2026-09-01 12:50 UTCEG score recompute
  3. 2026-09-01 05:44 UTCEG score recompute
  4. 2026-09-01 04:31 UTCEG score recompute
  5. 2026-09-01 04:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82747?
CVE-2026-82747 is a medium vulnerability published on September 1, 2026. Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor. When a resource has an accesstype :runtime read policy (a check evaluated per record rather than compiled to a filter), Ash.Policy.Authorizer decides each record in checkresult/1…
When was CVE-2026-82747 disclosed?
CVE-2026-82747 was first published in the National Vulnerability Database on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82747 actively exploited?
CVE-2026-82747 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-82747?
CVE-2026-82747 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-82747?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82747, 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-82747

Explore →

Is Your Infrastructure Affected by CVE-2026-82747?

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