Incorrect Authorization Affecting ash package, versions <3.6.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-HEX-ASH-13539511
- published13 Oct 2025
- disclosed13 Oct 2025
- creditJonatan Männchen
Introduced: 13 Oct 2025
NewCVE-2025-48043 (opens in a new tab)How to fix?
Upgrade ash to version 3.6.2 or higher.
Overview
ash is an A declarative, extensible framework for building Elixir applications.
Affected versions of this package are vulnerable to Incorrect Authorization in the Ash.Policy.Policy.compile_policy_expression/1 and Ash.Policy.Authorizer policies. An attacker can access unauthorized data by crafting requests that exploit permissive query filters generated under certain bypass or runtime policy conditions. This is only exploitable if filter-based authorization is used and bypass blocks with runtime-only conditions are defined without subsequent policies, or if runtime checks simplify to an empty scenario for a clause.
##Workaround
This vulnerability can be mitigated by avoiding bypass policies with runtime-only conditions, adding an explicit final forbid_if always() guard for sensitive reads, or restructuring checks to avoid empty SAT scenarios.