Quick answers
- Is CVE-2026-46395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46395 being exploited in the wild.
- How severe is CVE-2026-46395?
- Critical severity, with a CVSS score of 4, published 5 June 2026.
- Which products and versions are affected?
- HAX the Web HAXcms Node.js <= 25.0.0; @haxtheweb/haxcms-nodejs (npm) <= 25.0.0, SEMVER:introduced=0,fixed=26.0.0.
- Is there a fix for CVE-2026-46395?
- Yes. @haxtheweb/haxcms-nodejs (npm): upgrade to 26.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46395 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46395?
- Check whether you run HAX the Web HAXcms Node.js or @haxtheweb/haxcms-nodejs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @haxtheweb/haxcms-nodejs (npm): upgrade to 26.0.0 or later
npm install @haxtheweb/haxcms-nodejs@26.0.0
Technical details
The `hmacBase64()` function in the HAXcms Node.js backend suffers from two critical implementation flaws: it uses a hardcoded HMAC key ("0") and appends the actual system private key and salt directly to the output buffer before Base64 encoding. Because the `/system/api/connectionSettings` endpoint is unauthenticated and returns tokens generated by this function, an attacker can perform a single GET request to retrieve the tokens, decode them, and extract the plaintext private key. With this key, the attacker can forge valid JWTs for any user, including the 'admin' account, to gain full administrative access to the CMS. This issue only affects the Node.js implementation; the PHP backend is not vulnerable. The vulnerability is resolved in version 26.0.0.
Affected products
- HAXtheWeb HAXcms Node.js backend < 26.0.0
Identifiers
- CVE-2026-46395
- GHSA-6c8g-9hfh-pq5h
Timeline
- 2026-05-12: advisory: Original GitHub security advisory published
- 2026-06-05: disclosed: NVD publication date