An incorrect authorization vulnerability in the ash_phoenix library allows authenticated users to potentially bypass tenant-scoped access controls, posing a significant risk to data isolation.

The vulnerability exists in the SubdomainHook authorization callback, which executes before the tenant assignment is fully processed by the LiveView lifecycle. This results in the authorization logic evaluating a nil tenant, which may cause the application to default to a permissive state for authenticated users.

The failure to properly enforce tenant isolation can lead to unauthorized access to sensitive data belonging to other tenants within a multi-tenant environment. Given the CVSS score of 7.6, this vulnerability is classified as High severity, as it directly compromises the integrity and confidentiality of customer data and undermines the fundamental security architecture of the application.

Immediate Action: Update the ash_phoenix library to version 2.3.25 or later to ensure that tenant-scoped authorization checks are correctly synchronized with the LiveView navigation lifecycle.

Proactive Monitoring: Review application logs for unusual access patterns, specifically focusing on cross-tenant requests or unexpected authorization errors following recent deployments.

Compensating Controls: Ensure that secondary authorization checks are implemented at the data access or repository layer, which serves as a fail-safe if the application-level hook is bypassed.

Public Exploit Available: No

This vulnerability represents a significant risk to multi-tenant architectures by weakening core access control mechanisms. Administrators should prioritize upgrading the affected ash_phoenix dependency across all environments immediately to prevent potential data leakage or unauthorized cross-tenant access.