Quick answers
- Is CVE-2026-75757 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75757 being exploited in the wild.
- How severe is CVE-2026-75757?
- Informational severity, published 31 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Admin 0.9.1 to before 1.3.1.
- Is there a fix for CVE-2026-75757?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75757 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75757?
- Check whether you run Ash-Project Ash Admin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a cookie validation failure (CWE-347) in ash_admin's client-side JavaScript. The code reads session-state cookies by matching cookie names against document.cookie using an unanchored regular expression (new RegExp(name + "=([^;]+)")), which matches any cookie whose name merely ends with the requested name. Since cookies are shared across a registrable domain via the Domain attribute, a compromised sibling subdomain can set shadowing cookies (e.g., "xactor_authorizing" to match "actor_authorizing") that flow unvalidated into the LiveSocket connect parameters. No authentication is required; the attack vector is network-based and depends only on subdomain compromise. The fix validates cookie names by exact equality rather than substring matching.
Affected products
- ash-project ash_admin 0.9.1 to before 1.3.1
Timeline
- 2026-08-31: disclosed