# CVE-2025-4754: Missing Session Revocation on Logout in ash_authentication_phoenix

> Attackers can reuse stolen session tokens after logout because the library fails to revoke them, allowing unauthorized access until token expiry.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2025
- **Updated:** 22 Sep 2026
- **Also known as:** EEF-CVE-2025-4754, GHSA-f7gq-h8jv-h3cq

## What is CVE-2025-4754?

CVE-2025-4754 is a low-severity missing authorization vulnerability in team-alembic ash_authentication_phoenix, published on 17 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insufficient Session Expiration vulnerability in team-alembic ash_authentication_phoenix allows a session token captured before sign-out to remain usable afterwards.

The default sign_out/2 that AshAuthentication.Phoenix.Controller injects into an application's auth controller only calls Plug.Conn.clear_session/1. It never revokes the stored session or bearer tokens, so a token obtained before sign-out, through script injection, interception or device theft, keeps authenticating until its own expiry. Changing the password still revokes it.

This issue affects ash_authentication_phoenix: from 0.1.0 before 2.10.0.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-4754?

3 open source packages ship an affected version, including ash_authentication_phoenix.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_authentication_phoenix` | Hex | All versions | 2.10.0 |
| `ash_authentication_phoenix` | Hex | All versions | 2.10.0 |
| `ash_authentication_phoenix` | Hex | From 0.1.0 | 2.10.0 |

## How do I fix CVE-2025-4754?

Upgrade ash_authentication_phoenix to 2.10.0 or later.

## Is CVE-2025-4754 being exploited?

There is no known exploitation of CVE-2025-4754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4754 and fix it if it is affected.

What it is: CVE-2025-4754 is a low-severity missing authorization vulnerability in team-alembic ash_authentication_phoenix, published on 17 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-4754 in the wild and no public exploit code.

Affected packages and fixed versions:
- ash_authentication_phoenix (Hex): affected all versions; fixed in 2.10.0
- ash_authentication_phoenix (Hex): affected all versions; fixed in 2.10.0
- ash_authentication_phoenix (Hex): affected from 0.1.0; fixed in 2.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4754/ (Markdown: https://insights.sbomify.com/CVE-2025-4754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4754
- OSV: https://osv.dev/vulnerability/CVE-2025-4754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4754/
Summaries are generated and may contain mistakes; the official description above is the record.