# CVE-2026-110104: novel through 3.5.0 Unsalted MD5 Password Storage

> Attackers can recover plaintext passwords from unsalted MD5 hashes if the database is leaked, enabling credential reuse and account takeover.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-25gx-36j3-jw66

## What is CVE-2026-110104?

CVE-2026-110104 is a high-severity vulnerability in xxyopen novel, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xxyopen novel through 3.5.0 contains a weak password hashing vulnerability that allows attackers to recover plaintext passwords because UserServiceImpl.register() stores unsalted MD5 digests in user_info.password. Attackers who obtain the password column through a database leak or backup exposure can crack hashes with precomputed tables or GPU brute force and reuse credentials.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2026-110104?


## How do I fix CVE-2026-110104?

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

## Is CVE-2026-110104 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110104 and fix it if it is affected.

What it is: CVE-2026-110104 is a high-severity vulnerability in xxyopen novel, published on 13 Oct 2026. 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-2026-110104 exists.

Affected product: xxyopen novel. 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-2026-110104/ (Markdown: https://insights.sbomify.com/CVE-2026-110104/index.md)
```

## Sources

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

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