Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-48044 — ash

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-863 NVD
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Ash has authorization bypass when bypass policy condition evaluates to true

Summary

Bypass policies incorrectly authorize requests when their condition evaluates to true but their authorization checks fail and no other policies apply.

Impact

Resources with bypass policies can be accessed without proper authorization when:

  • Bypass condition evaluates to true
  • Bypass authorization checks fail
  • Other policies exist but their conditions don't match

Details

Vulnerable code in: [lib/ash/policy/policy.ex:69](https://github.com/ash-project/ash/blob/b2e4d625/lib/ash/policy/policy.ex#L69)

```elixir

{%{bypass?: true}, cond_expr, complete_expr}, {one_condition_matches, all_policies_match} ->

{

b(cond_expr or one_condition_matches), # <- Bug: uses condition only

b(complete_expr or all_policies_match)

}

```

The final authorization decision is: one_condition_matches AND all_policies_match

When a bypass condition is true but bypass policies fail, and subsequent policies have non-matching conditions:

1. one_condition_matches = cond_expr (bypass condition) = true (bug - should check if bypass actually authorizes)

2. all_policies_match = (complete_expr OR NOT cond_expr) for each policy

  • For non-matching policies: (false OR NOT false) = true (policies don't apply)

3. Final: true AND true = true (incorrectly authorized)

The bypass condition alone satisfies "at least one policy applies" even though the bypass fails to authorize.

Fix

Replace cond_expr with complete_expr on line 69:

```elixir

{%{bypass?: true}, _cond_expr, complete_expr}, {one_condition_matches, all_policies_match} ->

{

b(complete_expr or one_condition_matches), # <- Fixed

b(complete_expr or all_policies_match)

}

```

Line 52 should also be updated for consistency (though it's only triggered when bypass is the last policy, making it coincidentally safe in practice):

```elixir

{%{bypass?: true}, _cond_expr, complete_expr}, {one_condition_matches, true} ->

{

b(complete_expr or one_condition_matches), # <- For consistency

complete_expr

}

```

PoC

```elixir

policies do

bypass always() do

authorize_if actor_attribute_equals(:is_admin, true)

end

policy action_type(:read) do

authorize_if always()

end

end

```

Non-admin user can perform create actions (should be denied).

Test demonstrating the bug:

```elixir

test "bypass policy bug" do

policies = [

%Ash.Policy.Policy{

bypass?: true,

condition: [{Ash.Policy.Check.Static, result: true}], # condition = true

policies: [

%Ash.Policy.Check{

type: :authorize_if,

check: {Ash.Policy.Check.Static, result: false}, # policies = false

check_module: Ash.Policy.Check.Static,

check_opts: [result: false]

}

]

},

%Ash.Policy.Policy{

bypass?: false,

condition: [{Ash.Policy.Check.Static, result: false}],

policies: [

%Ash.Policy.Check{

type: :authorize_if,

check: {Ash.Policy.Check.Static, result: true},

check_module: Ash.Policy.Check.Static,

check_opts: [result: true]

}

]

}

]

expression = Ash.Policy.Policy.expression(policies, %{})

assert expression == false

# Expected: false (deny)

# Actual on main: true (incorrectly authorized)

end

```

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. Rated impact: confidentiality high, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Attack requirements: None — no deployment-specific condition has to hold.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: None.

Weakness class

CVE-2025-48044 is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

CVE-2025-48044 is recorded against 2 packages.

  • ash
  • unknown

Timeline and source

Published on 17 October 2025 and last revised on 30 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
cna.erlef.org (Web)
github.com (Package)
osv.dev (Web)

Other advisories for this package

ash has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-863: Incorrect Authorization) in other software:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CWE CWE-863
Public Exploit ✅ No
Source NVD
Published 2025-10-17
Updated 2026-08-20
Modified 2026-07-30

Affected Packages

Software From version Fixed in
ash
unknown

Similar Threats

Site Security Check

Is ash part of your stack?

CVE-2025-48044 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025