CVE-2026-106446

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-08. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-93969 (ENISA EUVD) · GHSA-8r5x-fm3f-whwj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.8%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Handlebars provides the power necessary to let users build semantic templates. From 4.0.0 until 4.7.10, Handlebars.compile() and Handlebars.precompile() accept pre-parsed AST objects while validating only selected PathExpression, NumberLiteral, and BooleanLiteral values. This issue bypasses the AST validation introduced in version 4.7.9 for CVE-2026-33937. An attacker who can supply an object instead of a template string can place JavaScript expressions in unchecked values such as Program.blockParams.length, a non-PathExpression parameter depth, a non-string StringLiteral.value, or a non-string PathExpression.original. The compiler emits those values into generated JavaScript, causing code execution in the server process when compile output renders or wherever precompile output is loaded. Applications that pass only template strings are not affected. This issue is fixed in version 4.7.10.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

October 6, 2026

Last Modified

October 7, 2026

Advisory Details (4)

Auto-updated Oct 31, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

JavaScript Injection via AST Type Confusion in compile (bypass of CVE-2026-33937) · Advisory · handlebars-lang/handlebars.js · GitHub

https://github.com/handlebars-lang/handlebars.js/security/advisories/GHSA-8r5x-fm3f-whwj
GitHub release Patch Available

v4.7.10

Patch available: handlebars-lang/handlebars.js v4.7.10

https://github.com/handlebars-lang/handlebars.js/releases/tag/v4.7.10
GitHub pull request Patch Available

Security improvements

Patch available: handlebars-lang/handlebars.js v4.7.10 (PR #2185 merged 2026-10-05)

https://github.com/handlebars-lang/handlebars.js/pull/2185
GitHub commit Patch Available

commit 703fdcc5fd6c (handlebars-lang/handlebars.js)

Patch available: handlebars-lang/handlebars.js v4.7.10 (contains commit 703fdcc5fd6c)

https://github.com/handlebars-lang/handlebars.js/commit/703fdcc5fd6cc8d1cc0c33cc19de40c467c4b8d2

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/console-rhel9:17928831112026-10-29redhat
redhatmulticluster-engine/console-mce-rhel9:17928867182026-10-29redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17930018272026-10-29redhat
npmhandlebars @ 4.7.10 (fixes >= 4.0.0, <= 4.7.9)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-handlebars3:4.7.10-1 ... 3:4.7.9-6 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-handlebars3:4.7.10-1 ... 3:4.7.9-6 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-handlebars3:4.7.7+~4.1.0-1 ... 3:4.7.9-6 (7 versions)
  • every version up to 3:4.7.10-1: fixed in 3:4.7.10-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
handlebars—
  • 4.0.0 up to 4.7.10: fixed in 4.7.10
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 68× 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.

  1. 2026-11-01 23:48 UTCEG score recompute
  2. 2026-11-01 23:48 UTCVendor advisory
  3. 2026-11-01 23:48 UTCGHSA enrichmentGHSA-8r5x-fm3f-whwj · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-8r5x-fm3f-whwj · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-01 08:00 UTCEG score recompute
  7. 2026-11-01 00:58 UTCEG score recompute
  8. 2026-11-01 00:58 UTCVendor advisory
  9. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-31 02:07 UTCEG score recompute
  11. 2026-10-31 02:07 UTCVendor advisory
  12. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-10-30 03:15 UTCEG score recompute
  14. 2026-10-30 03:15 UTCVendor advisory
  15. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  16. 2026-10-29 04:25 UTCEG score recompute
  17. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-10-28 05:29 UTCEG score recompute
  19. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-10-27 06:39 UTCEG score recompute
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-10-26 04:11 UTCEG score recompute
  23. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  24. 2026-10-25 14:54 UTCEG score recompute
  25. 2026-10-25 05:20 UTCEG score recompute
Show 43 more
  1. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-10-24 06:29 UTCEG score recompute
  3. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-10-23 07:38 UTCEG score recompute
  5. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-10-22 08:45 UTCEG score recompute
  7. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-21 09:54 UTCEG score recompute
  9. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-20 11:03 UTCEG score recompute
  11. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-19 12:11 UTCEG score recompute
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-18 05:08 UTCEG score recompute
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-17 06:57 UTCEG score recompute
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-16 08:04 UTCEG score recompute
  19. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  20. 2026-10-15 07:07 UTCEG score recompute
  21. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  22. 2026-10-14 02:58 UTCEG score recompute
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-12 16:39 UTCEG score recompute
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  26. 2026-10-11 20:14 UTCEG score recompute
  27. 2026-10-11 17:56 UTCEG score recompute
  28. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  29. 2026-10-11 13:42 UTCEG score recompute
  30. 2026-10-10 22:13 UTCEG score recompute
  31. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  32. 2026-10-09 22:57 UTCEG score recompute
  33. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  34. 2026-10-08 19:36 UTCEG score recompute
  35. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  36. 2026-10-08 03:00 UTCEG score recompute
  37. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  38. 2026-10-07 23:09 UTCEG score recompute
  39. 2026-10-07 19:19 UTCEG score recompute
  40. 2026-10-07 18:47 UTCEG score recompute
  41. 2026-10-06 20:32 UTCEG score recompute
  42. 2026-10-06 19:52 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  43. 2026-10-06 19:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-106446?
CVE-2026-106446 is a critical-severity vulnerability; its CVE record was published on October 6, 2026. Handlebars provides the power necessary to let users build semantic templates. From 4.0.0 until 4.7.10, Handlebars.compile() and Handlebars.precompile() accept pre-parsed AST objects while validating only selected PathExpression, NumberLiteral, and BooleanLiteral values. This issue bypasses the AST…
When was the CVE record for CVE-2026-106446 published?
The CVE record for CVE-2026-106446 was published on October 6, 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 October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-106446 actively exploited?
CVE-2026-106446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106446?
CVE-2026-106446 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106446?
A fix for CVE-2026-106446 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106446 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-106446

Explore →

Is Your Infrastructure Affected by CVE-2026-106446?

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