# CVE-2025-55796: Weak cryptography in n/a

> Predictable MD5 tokens allow attackers to brute-force confirmation links, leading to unauthorized account access and takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-xfjh-gf9p-8qr6

## What is CVE-2025-55796?

CVE-2025-55796 is a high-severity vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The openml/openml.org web application version v2.0.20241110 uses predictable MD5-based tokens for critical user workflows such as signup confirmation, password resets, email confirmation resends, and email change confirmation. These tokens are generated by hashing the current timestamp formatted as "%d %H:%M:%S" without incorporating any user-specific data or cryptographic randomness. This predictability allows remote attackers to brute-force valid tokens within a small time window, enabling unauthorized account confirmation, password resets, and email change approvals, potentially leading to account takeover.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Openml Openml Frontend.

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

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

## Is CVE-2025-55796 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-55795](https://insights.sbomify.com/CVE-2025-55795/): Business logic in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55796 is a high-severity vulnerability in n/a, published on 18 Nov 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-55796 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-55796/ (Markdown: https://insights.sbomify.com/CVE-2025-55796/index.md)
```

## Sources

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

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