# CVE-2025-14261: Lack of entropy allows registered low-privileged users of Litmus to crack valid JWT tokens and gain admin privileges

> Low-privileged users can crack weak JWT secrets to gain admin privileges in the Litmus platform.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-836x-3v5w-54f3

## What is CVE-2025-14261?

CVE-2025-14261 is a high-severity vulnerability in Litmuschaos litmus, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Litmus platform uses JWT for authentication and authorization, but the secret being used for signing the JWT is only 6 bytes long at its core, which makes it extremely easy to crack.

Weakness: CWE-331 (Insufficient Entropy)

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


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

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

## Is CVE-2025-14261 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14261 is a high-severity vulnerability in Litmuschaos litmus, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14261 in the wild and no public exploit code.

Affected product: Litmuschaos litmus. 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-14261/ (Markdown: https://insights.sbomify.com/CVE-2025-14261/index.md)
```

## Sources

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

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