VulnerabilityPublished 14 Dec 2025Updated 15 Dec 2025

CVE-2025-14651: MartialBE one-hub · Use of Hard-coded Cryptographic Key

Affects MartialBE one-hubSource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmartialbe/one-hub`pkg:github/martialbe/one-hub`Other threats	Affected 0.14.0 – 0.14.27 28 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-14651, European organizations should immediately audit all MartialBE one-hub deployments to identify usage of the default docker-compose.yml configuration and the SESSION_SECRET environment variable. Replace any hard-coded or default SESSION_SECRET values with strong, randomly generated secrets unique to each deployment. Implement automated configuration management and secrets management tools to enforce secure environment variable handling. Avoid deploying default example configurations in production environments. Additionally, restrict network access to the one-hub service using firewalls or zero-trust network principles to reduce exposure. Monitor logs for unusual session activity that could indicate exploitation attempts. Stay updated with MartialBE vendor advisories for patches or updated configuration guidelines. Consider container security best practices such as image scanning and runtime protection to detect anomalous behavior. Finally, integrate these controls into the organization's broader security policy and incident response plans to ensure rapid detection and remediation of potential exploitation.

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!"

Impact

For European organizations, the primary impact of CVE-2025-14651 lies in the potential compromise of session confidentiality and cryptographic protections within MartialBE one-hub deployments. Organizations using this product with default or unchanged SESSION_SECRET values risk session hijacking, unauthorized access, or data exposure. This is particularly critical for sectors handling sensitive personal data, such as finance, healthcare, or government services, where session integrity is vital. The medium severity and high attack complexity reduce the likelihood of widespread exploitation but do not eliminate risk, especially from targeted attackers with resources to analyze and exploit the vulnerability. The use of container orchestration and microservices in European enterprises means that this vulnerability could serve as an entry point for lateral movement if not mitigated. Additionally, compliance with GDPR and other data protection regulations could be jeopardized if session secrets are compromised, leading to potential legal and reputational consequences. Organizations relying on MartialBE one-hub for collaboration or data management should prioritize remediation to maintain confidentiality and trust.

Summary

The vulnerability identified as CVE-2025-14651 affects MartialBE one-hub versions up to 0.14.27 and stems from the use of a hard-coded cryptographic key within the docker-compose.yml configuration file, specifically through the SESSION_SECRET environment variable. This secret is used to secure session management or cryptographic operations, and hard-coding it means the same secret is reused across deployments, making it predictable and vulnerable to compromise. An attacker who can remotely access the service could exploit this weakness to hijack user sessions, decrypt sensitive data, or bypass authentication mechanisms relying on the SESSION_SECRET. The attack complexity is rated high, indicating that exploitation requires significant effort or specific conditions, and no privileges or user interaction are needed. The vulnerability does not affect integrity or availability directly but compromises confidentiality. The vendor explicitly states that the default docker-compose example is not intended for production use and urges administrators to customize all configurations and environment variables, including SESSION_SECRET, to unique, secure values. No patches or fixes are currently linked, and no known exploits are reported in the wild, but public disclosure means attackers could develop exploits. The CVSS 4.0 score is 6.3 (medium), reflecting network attack vector, high complexity, no privileges, no user interaction, and limited confidentiality impact. This vulnerability highlights the risks of deploying default configurations in containerized environments without proper security hardening.

References

Community reviews

Loading reviews…