# CVE-2025-14651: MartialBE one-hub docker-compose.yml hard-coded key

> Attackers can exploit a hard-coded session secret in the default docker-compose configuration to bypass security controls.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-4wp6-2mc5-g5v5

## What is CVE-2025-14651?

CVE-2025-14651 is a medium-severity vulnerability in MartialBE one-hub, published on 14 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in MartialBE one-hub up to 0.14.27. This vulnerability affects unknown code of the file docker-compose.yml. The manipulation of the argument SESSION_SECRET leads to use of hard-coded cryptographic key
 . The attack may be initiated remotely. The complexity of an attack is rather high. It is stated that the exploitability is difficult. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. The code maintainer recommends (translated from Chinese): "The default docker-compose example file is not recommended for production use. If you intend to use it in production, please carefully check and modify every configuration and environment variable yourself!"

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

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

## Is CVE-2025-14651 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14651 is a medium-severity vulnerability in MartialBE one-hub, published on 14 Dec 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-14651 exists.

Affected product: MartialBE one-hub. 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-14651/ (Markdown: https://insights.sbomify.com/CVE-2025-14651/index.md)
```

## Sources

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

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