CVE intelligence and bounded remediation

CVE-2025-25202 — Ash Authentication is an authentication framework for Elixir applications

Medium CVSS 6.5

Ash Authentication is an authentication framework for Elixir applications. Applications which have been bootstrapped by the igniter installer present since AshAuthentication v4.1.0 and who have used the magic link strategy _or_ are manually revoking tokens are affected by revoked tokens being allowed to verify as valid. Unless one hase implemented any kind of custom token revocation feature in your application, then one will not be affected. The impact here for users using builtin functionality is that magic link tokens are reusable until they expire. With that said, magic link tokens are only valid for 10 minutes, so the surface area for abuse is extremely low here. The flaw is patched in version 4.4.9. Additionally a compile time warning is shown to users with remediation instructions if they upgrade. 4.4.9 ships with an upgrader, so those who use `mix igniter.upgrade ash_authentication` will have the necessary patch applied. Otherwise, one may run the upgrader manually as described in the error message. As a workaround, delete the generated `:revoked?` generic action in the token resource. This will cause it to use the one internal to Ash Authentication which has always been co…

Severity
Medium
CVSS
6.5 (3.1)
Published
2025-02-11
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-269

Affected products

  • alembic / ash_authentication

Matched remediation archetype

Privilege escalation and unsafe privilege management

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
  • Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
  • Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.

Remediate safely

  • Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
  • Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
  • Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.