# CVE-2025-61152: Auth bypass in n/a

> Attackers can bypass authentication by crafting unsigned JWT tokens if signature verification is disabled, leading to privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2025
- **Updated:** 25 Nov 2025
- **Also known as:** GHSA-28pv-f4g7-364j, UBUNTU-CVE-2025-61152

## What is CVE-2025-61152?

CVE-2025-61152 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded and accepted without any cryptographic signature verification. A malicious actor can craft a forged token with arbitrary claims (e.g., is_admin=true) and bypass authentication checks, leading to privilege escalation or unauthorized access in applications that rely on python-jose for token validation. This issue is exploitable unless developers explicitly reject 'alg=none' tokens, which is not enforced by the library. NOTE: all parties agree that the issue is not relevant because it only occurs in a "verify_signature": False situation.

Weakness: CWE-269 (Improper Privilege Management)

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


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

No fix has been published for CVE-2025-61152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61152 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61152 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61152 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-61152/ (Markdown: https://insights.sbomify.com/CVE-2025-61152/index.md)
```

## Sources

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

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