CVE-2026-12212: hcengineering Huly Platform · Improper Access Controls
Affects hcengineering Huly PlatformSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hcengineeringHuly Platform | Affected
| Fixed in– |
npmhcengineering/huly_platformpkg:npm/hcengineering/huly_platformOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:hcengineering:huly_platform:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor the vendor's communications for any future updates. Until a patch is released, consider restricting network access to the affected service and applying compensating controls to limit exposure to untrusted networks.
Description
CVE-2026-12212 is a medium severity vulnerability in hcengineering Huly Platform versions 0.1 through 0.7.0. It involves improper access controls in the getMailboxSecret function within the RPC Interface component. The vulnerability can be exploited remotely without user interaction or elevated privileges. The vendor has not responded to the disclosure, and no official patch or mitigation guidance is currently available.