CVE-2026-46395

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the hmacBase64() function in the HAXcms Node.js backend contains two critical cryptographic implementation errors that together allow any unauthenticated attacker to extract the system’s private signing key and forge arbitrary admin-level JSON Web Tokens (JWTs) allowing them to get full admin access with a single HTTP request. First, the function passes the literal string "0" as the HMAC signing key instead of the key parameter, making every HAXcms instance compute identical HMACs for the same input. Then, after computing the HMAC, the function concatenates the real key parameter which is "this.privateKey + this.salt", the system’s master signing secret is directly onto the output. The combined buffer is base64-encoded and returned as the token. Every base64url token produced has the same structure: 32 bytes HMAC keyed with "0" and N bytes of privateKey+salt. An attacker base64-decodes any token, discards the first 32 bytes, and reads the private key directly. The /system/api/connectionSettings endpoint is unauthenticated and returns multiple tokens generated by this function. A single GET request to this endpoint exposes the private key. The PHP backend implements this function correctly with the actual key and returns only the hash. The PHP version produces 44-character tokens whereas the broken Node.js version produces 139+ character tokens. Version 26.0.0 fixes the issue.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2026

Last Modified

June 5, 2026

Advisory Details (1)

Auto-updated Sep 23, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Private Key Disclosure via Broken HMAC Implementation · Advisory · haxtheweb/issues · GitHub

https://github.com/haxtheweb/issues/security/advisories/GHSA-6c8g-9hfh-pq5h

Vendor Advisories for CVE-2026-46395(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@haxtheweb/haxcms-nodejs—
  • every version up to 26.0.0: fixed in 26.0.0
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 151 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 52 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-12 16:02 UTCEG score recompute
  3. 2026-10-11 19:45 UTCEG score recompute
  4. 2026-10-11 17:00 UTCEG score recompute
  5. 2026-10-11 14:25 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 74 more
  1. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-08-23 17:05 UTCEG score recompute
  19. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-08-21 23:38 UTCEG score recompute
  22. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-08-20 19:02 UTCEG score recompute
  24. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-08-17 13:54 UTCEG score recompute
  27. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-08-17 10:00 UTCEG score recompute
  29. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  30. 2026-08-16 03:35 UTCEG score recompute
  31. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  32. 2026-08-15 01:46 UTCEG score recompute
  33. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-08-14 02:07 UTCEG score recompute
  35. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-08-12 15:53 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-08-11 13:54 UTCEG score recompute
  39. 2026-08-11 00:39 UTCEG score recompute
  40. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-08-09 17:19 UTCEG score recompute
  42. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-08-09 01:36 UTCEG score recompute
  44. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-08-07 18:07 UTCEG score recompute
  46. 2026-08-06 16:47 UTCEG score recompute
  47. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-05 21:21 UTCEG score recompute
  49. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-08-03 16:59 UTCEG score recompute
  53. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  54. 2026-08-02 05:56 UTCEG score recompute
  55. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  56. 2026-08-01 17:56 UTCEG score recompute
  57. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  60. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  61. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  62. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  63. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  64. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  65. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  66. 2026-07-23 03:17 UTCEG score recompute
  67. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  68. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  69. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  70. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  71. 2026-07-19 02:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  73. 2026-07-16 17:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  74. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Frequently asked(5)

What is CVE-2026-46395?
CVE-2026-46395 is a critical-severity vulnerability; its CVE record was published on May 19, 2026. HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the hmacBase64() function in the HAXcms Node.js backend contains two critical cryptographic implementation errors that together allow any unauthenticated attacker to extract the system’s private signing…
When was the CVE record for CVE-2026-46395 published?
The CVE record for CVE-2026-46395 was published on May 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 5, 2026; the record at its source may have been updated since.
Is CVE-2026-46395 actively exploited?
CVE-2026-46395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46395?
CVE-2026-46395 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46395?
A fix for CVE-2026-46395 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46395 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46395

Explore →

Is Your Infrastructure Affected by CVE-2026-46395?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.