Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-75757 – Session/Actor Hijacking via Cookie Confusion – ash_admin 0.9.1 to before 1.3.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-75757 is a cookie-validation vulnerability (CWE-565: Reliance on Cookies without Validation and Integrity Checking) in ash_admin, the admin UI package for the Ash Framework (Elixir). An attacker who controls a sibling subdomain of an application hosting ash_admin can plant crafted cookies that are silently accepted by the admin interface’s client-side JavaScript, allowing the attacker to rebind an administrator’s session to a different actor, tenant, or authorization mode. The issue carries a CVSS v4.0 base score of 8.3 (High) and affects versions 0.9.1 up to (but not including) 1.3.1.

Technical details

  • Root cause: The cookie-reading logic in the AshAdmin JavaScript bundle builds a regular expression as new RegExp(cookieName + "=([^;]+)") without anchoring the match to the start of the cookie name. As a result, the match succeeds against any cookie whose name merely ends with the requested cookie name rather than matching it exactly.
  • Trigger conditions: The attacker must control a sibling subdomain (or otherwise be able to set cookies scoped to a parent domain shared with the AshAdmin application) so that a maliciously named cookie is sent alongside the legitimate ones.
  • Attack vector: Network-based, no privileges required, no user interaction required beyond visiting/loading the admin page while attacker-set cookies are present (CVSS AV:N/AC:L/AT:P/PR:N/UI:N).
  • Impact: By planting a cookie such as xactor_authorizing=… or evil_actor_paused=…, an attacker can satisfy lookups for legitimate cookie names like actor_authorizing or actor_paused. These attacker-controlled values then flow unvalidated into the LiveSocket connection parameters used by AshAdmin, letting the attacker manipulate the acting actor, tenant context, or authorization mode of an administrator’s session — an integrity impact on session state (CVSS VI:H) without directly exposing confidentiality of other data.

Affected software

  • ash_admin (Elixir/Ash Framework admin UI package): versions >= 0.9.1 and < 1.3.1

Severity

  • CVSS v4.0 Base Score: 8.3 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
  • CWE: CWE-565 (Reliance on Cookies without Validation and Integrity Checking)

Mitigation and recommended actions

  • Immediate: Upgrade ash_admin to version 1.3.1 or later, which fixes the flaw by comparing cookie names for exact equality (splitting document.cookie on semicolons) instead of using an unanchored substring/regex match.
  • If immediate patching is not possible:
    • Avoid deploying AshAdmin on a domain that shares a parent domain with untrusted or third-party-controlled sibling subdomains.
    • Ensure strict subdomain isolation and cookie scoping (e.g., avoid overly broad Domain= attributes on cookies) so that sibling subdomains cannot set cookies visible to the AshAdmin origin.
    • Restrict access to the AshAdmin interface (e.g., via network-level access controls, VPN, or IP allowlisting) to reduce exposure until the patch can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge