cve.bz

CVE-2026-81852 AshAdmin ships a hardcoded CSP nonce, allowing nonce-based CSP bypass

2.1 lowEPSS 0.5%Fix available

Low (2.1) in ash-project ash admin. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in ash_admin 1.3.1.

On this page
Use of Insufficiently Random Values vulnerability in ash-project ash_admin ships a hardcoded, publicly known CSP nonce, defeating nonce-based Content-Security-Policy protection. When mounted without :csp_nonce_assign_key, AshAdmin.Router.ash_admin/2 defaulted the img, style, and script nonces to the literal constant ash_admin-Ed55GFnX, which AshAdmin.Layouts wrote verbatim into the nonce attribute of its inline <style> and <script> tags on every response. The value is a compile-time constant published in the repository and is never rotated per request. If an application's CSP script-src allow-lists that documented default, any HTML-injection sink on an admin page can reuse the known nonce to run inline scripts the policy was meant to block. The fix generates a fresh random nonce per request. This issue affects ash_admin: from 0.10.8 before 1.3.1.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-330 Use of Insufficiently Random Values
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash_admin (Hex): fixed in 1.3.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-81852 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-81852?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-81852?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-81852 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ash_adminfrom 0.10.8 before 1.3.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-81852Hexash_admin>=0.10.8 <1.3.11.3.1
EEF-CVE-2026-81852v1.3.0, v1.2.0, v1.1.0, v0.14.0, v0.13.26 and 47 moreno fix published

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-485 Signature Spoofing by Key Recreation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON