CVE-2026-81853

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

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

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

Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash_admin turns a record-lookup URL into an equality oracle over sensitive attributes.

AshAdmin.Helpers.decode_primary_key/2 decodes the composite-primary-key form (Base64 plus ETF) and returns the decoded map verbatim as the lookup filter, without checking that its keys are the resource's primary-key fields. The deserialization guards bound size, block new atoms and funs, and reject nested expressions, but none restricts which fields come back, and :safe still allows any already-interned attribute name. An attacker can therefore encode %{api_token: "guess"} and have it spliced into the lookup filter, brute-forcing a sensitive attribute value (API token, reset token) one equality guess at a time; Map.to_list/1 also accepts structs, yielding a bogus __struct__ key. The fix rejects any decoded key that is not a real primary-key field.

This issue affects ash_admin: from 0.1.0 before 1.3.1.

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

Published

August 31, 2026

Last Modified

September 1, 2026

References (5)

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_admin0.1.0 ... 1.3.0 (119 versions)1.3.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 25× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-17 20:48 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-14 13:56 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:48 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-08 05:40 UTCEG score recompute
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-05 01:30 UTCEG score recompute
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 21:22 UTCEG score recompute
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 04:40 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-31 16:24 UTCEG score recompute
  22. 2026-08-31 16:15 UTCEG score recompute
  23. 2026-08-31 03:19 UTCEG score recompute
  24. 2026-08-31 02:49 UTCEG score recompute
  25. 2026-08-31 02:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81853?
CVE-2026-81853 is a low vulnerability published on August 31, 2026. Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash_admin turns a record-lookup URL into an equality oracle over sensitive attributes. AshAdmin.Helpers.decodeprimarykey/2 decodes the composite-primary-key form (Base64 plus ETF) and returns the decoded map verbatim as…
When was CVE-2026-81853 disclosed?
CVE-2026-81853 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update 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-81853 actively exploited?
CVE-2026-81853 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 82.1% of all scored CVEs.
What is the CVSS score of CVE-2026-81853?
CVE-2026-81853 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2026-81853?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81853, 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-81853

Explore →

Is Your Infrastructure Affected by CVE-2026-81853?

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

Start Free Scan →Browse All CVEs