Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Impact | The CVSS v3.1 score of 3.7 reflects a low-severity profile: network-accessible attack vector (AV:N) but high complexity (AC:H) requiring significant skill and effort to exploit. The vector indicates unauthenticated access (PR:N) with integrity impact only (I:L), no confidentiality or availability impact. The exploit proof-of-concept indicator (E:P) suggests experimental or limited evidence of exploitability. Cross-referencing signals: high attack complexity (AC:H) and the vendor's non-response suggest this is not trivial to weaponize despite the remote attack vector. The absence of EPSS probability data and no CISA KEV confirmation indicate this is not a high-priority active threat. SSVC framework assessment suggests automatable exploitation is unlikely due to AC:H; technical impact is limited to token integrity, not system compromise. This is a valid cryptographic weakness but in a specific component with non-trivial exploitation barriers-priority should be moderate rather than critical. |
| Exploit ScenarioDerived | An attacker with network access to a Huly Platform instance could craft malicious JWT tokens by reverse-engineering or predicting the hard-coded cryptographic key used by the token.ts component. By manipulating the SERVER_SECRET argument to reveal or reuse the embedded key material, the attacker could generate forged authentication tokens to bypass token validation or impersonate legitimate users. However, the high attack complexity (AC:H) means the attacker must possess significant cryptographic expertise and understanding of the platform's internal token structure; no public exploit code has been identified, making this a theoretical but viable attack vector requiring specialized knowledge rather than automated exploitation tools. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 06, 2026
JWT token handling in hcengineering Huly Platform 0.7.382 uses hard-coded cryptographic keys in the token.ts component, allowing remote attackers to forge or manipulate authentication tokens with high attack complexity. The vulnerability affects confidentiality and integrity of token-based authentication but requires significant technical effort to exploit, reflected in a low CVSS score (3.7) and high attack complexity rating. No active exploitation has been confirmed, and the vendor has not responded to disclosure attempts.
RemediationAI
Immediate remediation requires removal of hard-coded cryptographic keys from the JWT Token Handler and implementation of secure secret management for the SERVER_SECRET parameter. Users should upgrade to a patched version of Huly Platform once released by hcengineering; however, no vendor-released patch version has been independently confirmed at time of analysis. As an interim workaround, restrict network access to the JWT token endpoint and implement additional authentication layers (e.g., API gateway token validation) to limit token forging risk. Ensure that the SERVER_SECRET parameter is sourced from secure configuration management (environment variables, vault systems) rather than hard-coded values. Monitor hcengineering's official repository (https://vuldb.com/submit/785631) and security advisories for patch announcements, and consider contacting the vendor directly for remediation timeline if this affects production systems.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the JWT Token Handler functionality within hcengineering Huly Platform's foundations/core/packages/token/src/token.ts file. The root cause is classified under CWE-321 (Use of Hard-Coded Cryptographic Key), a critical weakness where security-sensitive cryptographic operations depend on static, embedded keys rather than dynamically managed secrets. The SERVER_SECRET parameter accepts user-supplied input that leads to reuse of hard-coded cryptographic material, compromising the security model of JSON Web Token generation and validation. This affects the entire Huly Platform product line across all versions in the CPE range, as the vulnerability exists in core JWT token handling infrastructure.
Know when Huly Platform gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was determined in hcengineering Huly Platform 0.7.382. Affected by this issue is some unknown functionality of the file foundations/core/packages/token/src/token.ts of the component JWT Token Handler. This manipulation of the argument SERVER_SECRET with the input secret causes use of hard-coded cryptographic key . The attack can be initiated remotely. The attack is considered to have high complexity. The exploitation is known to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-19172
GHSA-x32v-jmqh-4323
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB