JWT token forgery via hard-coded signing key
Published Apr 6, 2026 · Updated Apr 6, 2026
Hard-coded cryptographic key use in Huly Platform 0.7.382 allows remote attackers to forge JWT tokens through the token handler. The token.ts handler uses the literal SERVER_SECRET value secret as the shared JWT signing key without rejecting the documented default. The affected deployment must retain that default key; forged tokens compromise authentication integrity, with no reported data disclosure or service interruption.
Summary
What happened
Hard-coded cryptographic key use in Huly Platform 0.7.382 allows remote attackers to forge JWT tokens through the token handler. The token.ts handler uses the literal SERVER_SECRET value secret as the shared JWT signing key without rejecting the documented default. The affected deployment must retain that default key; forged tokens compromise authentication integrity, with no reported data disclosure or service interruption.
The record
- CVE
- CVE-2026-5622
- Published
- Apr 6, 2026
- Updated
- Apr 6, 2026
- Vendor
- Huly Labs
- Product
- Huly Platform
- Classifications
- CWE-321, CWE-320
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2026CVE publishedPublication date reported by the CVE source.
- Apr 6, 2026Record 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.7.382
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.
Public exploit references
No public exploit references are available in this record.
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