CVE-2025-48044: Authorization bypass when bypass policy condition evaluates to true
Incorrect Authorization vulnerability in ash-project ash allows Authentication Bypass. This vulnerability is associated with program files lib/ash/policy/policy.ex and program routines 'Elixir.Ash.Policy.Policy':expression/2.
This issue affects ash: from 3.6.3 before 3.7.1.
Security readout for executives and security teams
Plain-English summary
Ash applications using affected authorization policies may let a low-privileged user bypass intended access controls when a bypass-policy condition evaluates as true. Successful abuse could expose or alter sensitive application data. Availability impact is not identified. The issue is remotely reachable and low complexity according to CVSS 4.0.
Executive priority
Treat as a high-priority authorization defect. Promptly identify internet-facing or sensitive-data applications using affected Ash versions, then upgrade and test access controls. Escalate systems where bypass policies govern confidential records or privileged changes. There is no supplied evidence of active exploitation.
Technical view
CVE-2025-48044 is an incorrect-authorization flaw, CWE-863, in Ash policy expression handling, associated with lib/ash/policy/policy.ex and expression/2. It affects Ash versions from 3.6.3 through versions before 3.7.1. The supplied CVSS 4.0 score is 8.6, with network access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is likely where an Elixir application runs Ash 3.6.3 to below 3.7.1 and relies on affected bypass-policy conditions for authorization. Actual risk depends on application policy configuration and protected resources. The bundle does not establish which deployments or downstream applications are affected.
Exploitation context
The source bundle provides no evidence of public exploitation or exploit availability, and the CVE is not listed as KEV. This does not prove exploitation is absent. The CVSS vector indicates a remote, low-privileged attacker could potentially trigger the flaw without user interaction.
Researcher notes
The affected interval is stated as 3.6.3 through versions before 3.7.1, while structured affected entries also reference a specific repository commit. Validate exposure using both the resolved package version and vendor advisory. The bundle attributes the flaw to policy expression handling but does not provide enough detail to characterize every vulnerable policy pattern.
Mitigation direction
Upgrade Ash to version 3.7.1 or later according to the stated affected range.
Review the vendor advisory before deployment for any release-specific requirements.
Prioritize applications whose bypass policies protect sensitive reads or writes.
Apply compensating authorization checks if an immediate upgrade is impossible.
Validation and detection
Inventory deployed Ash versions, including locked transitive dependencies.
Identify authorization policies containing bypass conditions in affected applications.
Confirm production resolves Ash 3.7.1 or later after remediation.
Test that low-privileged users cannot access or modify protected resources.
Review access logs for unexpected successful actions by low-privileged accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.