Skip to content
Threat Brief

← All advisories

CVE-2026-75757

High 8.3No known exploitationFix available

AshAdmin cookie reader matches names by substring, enabling actor/session shadowing from a sibling subdomain

Record last updated

CVSS score

8.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 33% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Reliance on Cookies without Validation and Integrity Checking vulnerability in ash-project ash_admin lets an attacker who controls a sibling subdomain rebind an admin's session to a different actor, tenant, or authorization mode. AshAdmin's client JavaScript read its state cookies (tenant, actor_resource, actor_primary_key, actor_action, actor_domain, actor_authorizing, actor_paused) by matching the cookie name with an unanchored regular expression (new RegExp(name + "=([^;]+)")) against the whole document.cookie. Any cookie whose name merely ends with the requested name therefore matches, and whichever is serialized first wins. Because cookies are shared across a registrable domain, a compromised sibling subdomain can set a shadowing cookie (for example xactor_authorizing) with Domain=.example.com that flows unvalidated into the admin's LiveSocket connect params. The fix matches cookie names by exact equality. This issue affects ash_admin: from 0.9.1 before 1.3.1.

Weakness: CWE-565

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ash-projectash_adminfrom 0.9.1 before 1.3.11.3.1CVE Program
ash-projectash_adminfrom 77a43cc4fa04cb59c38fc434568a35a38ecb995a before e93a3408a85035e1f90275d02bc2470c96095e56e93a3408a85035e1f90275d02bc2470c96095e56CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references