# CVE-2026-5622: hcengineering Huly Platform JWT Token token.ts hard-coded key

> Hard-coded JWT secret in Huly Platform allows remote attackers to bypass authentication mechanisms, requiring high complexity to exploit.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-x32v-jmqh-4323

## What is CVE-2026-5622?

CVE-2026-5622 is a medium-severity vulnerability in hcengineering Huly Platform, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

## Which versions are affected by CVE-2026-5622?


## How do I fix CVE-2026-5622?

No fix has been published for CVE-2026-5622 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5622 being exploited?

There is no known exploitation of CVE-2026-5622 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5622 and fix it if it is affected.

What it is: CVE-2026-5622 is a medium-severity vulnerability in hcengineering Huly Platform, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5622 in the wild and no public exploit code.

Affected product: hcengineering Huly Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5622/ (Markdown: https://insights.sbomify.com/CVE-2026-5622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5622
- OSV: https://osv.dev/vulnerability/CVE-2026-5622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5622/
Summaries are generated and may contain mistakes; the official description above is the record.