Skip to content
Threat Brief

← All advisories

CVE-2026-82724

High 7.6No known exploitationFix available

Broken access control in AshPhoenix SubdomainHook via a nil tenant in handle_subdomain

Record last updated

CVSS score

7.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

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

CISA remediation deadline

None

Not in the KEV catalog

Description

Incorrect Authorization vulnerability in ash-project ash_phoenix invokes the SubdomainHook authorization callback with a nil tenant, so tenant-scoped access checks never see the tenant they are meant to enforce. AshPhoenix.LiveView.SubdomainHook.on_mount/4 attached a handle_params hook to assign the tenant and then immediately called handle_subdomain in the same on_mount. The tenant assign is only written when LiveView later runs handle_params, strictly after on_mount returns, so handle_subdomain read an unset assign and ran as apply(m, f, [socket, nil | a]). A consumer gate that halts when the user does not belong to the tenant instead evaluated nil, either crashing or taking a permissive branch, and it was never re-run once the real subdomain was assigned or on later navigations. The fix runs handle_subdomain inside the handle_params hook with the real tenant on every navigation. This issue affects ash_phoenix: from 2.1.26 before 2.3.25.

Weakness: CWE-863

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_phoenixfrom 2.1.26 before 2.3.252.3.25CVE Program
ash-projectash_phoenixfrom 9a5ea4d377bc263de321d79574872a3dfc4fb541 before b396e1aa5c6bdec39255f19cf938b539e6d28b71b396e1aa5c6bdec39255f19cf938b539e6d28b71CVE 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