Administrative session forgery via default signing key
Published Dec 14, 2025 · Updated Dec 14, 2025
Hard-coded session secrets in MartialBE One Hub 0.14.0 through 0.14.27 allow remote attackers to forge administrative sessions. The supplied docker-compose.yml assigns SESSION_SECRET the fixed value random_string, which Gorilla securecookie accepts as the signing key for attacker-created session data. Exploitation requires a deployment that retains the example value; a forged cookie can claim the root identity and administrator role to reach sensitive backend interfaces.
Summary
What happened
Hard-coded session secrets in MartialBE One Hub 0.14.0 through 0.14.27 allow remote attackers to forge administrative sessions. The supplied docker-compose.yml assigns SESSION_SECRET the fixed value random_string, which Gorilla securecookie accepts as the signing key for attacker-created session data. Exploitation requires a deployment that retains the example value; a forged cookie can claim the root identity and administrator role to reach sensitive backend interfaces.
The record
- CVE
- CVE-2025-14651
- Published
- Dec 14, 2025
- Updated
- Dec 14, 2025
- Vendor
- MartialBE
- Product
- One Hub
- Classifications
- CWE-321, CWE-320, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2025CVE publishedPublication date reported by the CVE source.
- Dec 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.14.0
- Affected versionversion=0.14.1
- Affected versionversion=0.14.10
- Affected versionversion=0.14.11
- Affected versionversion=0.14.12
- Affected versionversion=0.14.13
- Affected versionversion=0.14.14
- Affected versionversion=0.14.15
- Affected versionversion=0.14.16
- Affected versionversion=0.14.17
- Affected versionversion=0.14.18
- Affected versionversion=0.14.19
- Affected versionversion=0.14.2
- Affected versionversion=0.14.20
- Affected versionversion=0.14.21
- Affected versionversion=0.14.22
- Affected versionversion=0.14.23
- Affected versionversion=0.14.24
- Affected versionversion=0.14.25
- Affected versionversion=0.14.26
- Affected versionversion=0.14.27
- Affected versionversion=0.14.3
- Affected versionversion=0.14.4
- Affected versionversion=0.14.5
- Affected versionversion=0.14.6
- Affected versionversion=0.14.7
- Affected versionversion=0.14.8
- Affected versionversion=0.14.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- One Hub SESSION_SECRET session-forgery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo