Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-5622: Use of Hard-coded Cryptographic Key in hcengineering Huly Platform

0
Medium
VulnerabilityCVE-2026-5622cvecve-2026-5622
Published: Mon Apr 06 2026 (04/06/2026, 04:30:13 UTC)
Source: CVE Database V5
Vendor/Project: hcengineering
Product: Huly Platform

Description

CVE-2026-5622 is a medium severity vulnerability in hcengineering Huly Platform version 0. 7. 382 involving the use of a hard-coded cryptographic key in the JWT Token Handler component. The issue arises from manipulation of the SERVER_SECRET argument, leading to use of a fixed cryptographic key. The vulnerability can be exploited remotely but requires high attack complexity, making exploitation difficult. The vendor has not responded to the disclosure, and no patch or remediation guidance is currently available.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/13/2026, 15:06:46 UTC

Technical Analysis

This vulnerability affects the JWT Token Handler in the hcengineering Huly Platform 0.7.382, specifically in the file foundations/core/packages/token/src/token.ts. It involves the use of a hard-coded cryptographic key due to manipulation of the SERVER_SECRET input. The vulnerability allows remote attackers to potentially exploit the system, but the attack complexity is high, and no privileges or user interaction are required. The CVSS 4.0 base score is 6.3, indicating medium severity. The vendor has not provided any response or patch to date.

Potential Impact

The vulnerability could allow remote attackers to compromise the cryptographic integrity of JWT tokens by exploiting the hard-coded key, potentially leading to unauthorized token creation or validation bypass. However, the high attack complexity and lack of known exploits in the wild reduce the immediate risk. No privilege or user interaction is required for the attack, but the impact is limited by the difficulty of exploitation.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded and no official fix is available, users should consider mitigating risk by restricting access to the affected component, monitoring for suspicious token activity, and avoiding use of the affected version if possible until a patch or official guidance is released.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-04-05T16:06:11.825Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69d33a730a160ebd9261d5bc

Added to database: 4/6/2026, 4:45:39 AM

Last enriched: 4/13/2026, 3:06:46 PM

Last updated: 5/21/2026, 12:51:38 PM

Views: 81

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses