CVE-2026-106445

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th 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

Also known asEUVD-2026-93952 (ENISA EUVD) · GHSA-p8wg-vrv2-v86f (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.2Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Handlebars provides the power necessary to let users build semantic templates. From 3.0.0 until 4.7.10, Handlebars lookupProperty returns Function.prototype.constructor before applying the prototype-access deny list because constructor is an own property of Function.prototype. When an attacker can render a controlled template with allowProtoMethodsByDefault enabled and an accessible function in the template context, the template can traverse from that function through its prototype to Function.prototype and then obtain the Function constructor through the own-property bypass. This permits attacker-controlled JavaScript to execute with the server application's privileges. This issue is fixed in version 4.7.10.

CVSS
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 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.6%
EPSS %ILE
48th
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.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 12, 2026

Advisory Details (4)

Auto-updated Oct 6, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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 commit Patch Available

commit ceec388abe1d (handlebars-lang/handlebars.js)

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

https://github.com/handlebars-lang/handlebars.js/commit/ceec388abe1d1aac8f6369860d5f390fa71ef4fa
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 advisoryMentions a patch (unverified)

JavaScript Injection via Own Property Check Bypass · Advisory · handlebars-lang/handlebars.js · GitHub

https://github.com/handlebars-lang/handlebars.js/security/advisories/GHSA-p8wg-vrv2-v86f

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-192026-11-04redhat
redhatmulticluster-engine/console-mce-rhel9:17928867182026-10-29redhat
redhatrhacm2/console-rhel9:17928831112026-10-29redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17930018272026-10-29redhat
npmhandlebars @ 4.7.10 (fixes >= 3.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—
  • 3.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 20× in last 7d / 60× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 116 rows 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. None are among the latest 100 rows. The 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-12 23:05 UTCEchelonGraph re-scored
  3. 2026-11-12 23:05 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-11-12 00:49 UTCEchelonGraph re-scored
  6. 2026-11-12 00:49 UTCVendor advisory
  7. 2026-11-12 00:49 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  8. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-11-11 02:33 UTCEchelonGraph re-scored
  10. 2026-11-11 02:33 UTCVendor advisory
  11. 2026-11-11 02:33 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  12. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-11-10 06:13 UTCEchelonGraph re-scored
  14. 2026-11-10 06:13 UTCVendor advisory
  15. 2026-11-10 06:13 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  16. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-11-09 07:57 UTCEchelonGraph re-scored
  18. 2026-11-09 07:57 UTCVendor advisory
  19. 2026-11-09 07:57 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  20. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-11-08 09:42 UTCEchelonGraph re-scored
  22. 2026-11-08 09:42 UTCVendor advisory
  23. 2026-11-08 09:42 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  24. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-11-07 11:26 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 11:26 UTCVendor advisory
  2. 2026-11-07 11:26 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  3. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-11-06 13:11 UTCEchelonGraph re-scored
  5. 2026-11-06 13:11 UTCVendor advisory
  6. 2026-11-06 13:11 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  7. 2026-11-05 22:25 UTCOSV refresh
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-11-05 14:54 UTCVendor advisory
  10. 2026-11-05 14:54 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  11. 2026-11-04 16:38 UTCEchelonGraph re-scored
  12. 2026-11-04 16:38 UTCVendor advisory
  13. 2026-11-04 16:38 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-11-03 18:22 UTCEchelonGraph re-scored
  16. 2026-11-03 18:22 UTCVendor advisory
  17. 2026-11-03 18:22 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  18. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-11-03 01:10 UTCEchelonGraph re-scored
  20. 2026-11-03 01:10 UTCVendor advisory
  21. 2026-11-03 01:10 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  22. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-11-02 02:49 UTCEchelonGraph re-scored
  24. 2026-11-02 02:49 UTCVendor advisory
  25. 2026-11-02 02:49 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  26. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  27. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-p8wg-vrv2-v86f · GitHub severity CRITICAL
  28. 2026-11-01 04:33 UTCEchelonGraph re-scored
  29. 2026-11-01 04:33 UTCVendor advisory
  30. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  31. 2026-10-31 06:17 UTCEchelonGraph re-scored
  32. 2026-10-31 06:17 UTCVendor advisory
  33. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  34. 2026-10-30 08:02 UTCEchelonGraph re-scored
  35. 2026-10-30 08:02 UTCVendor advisory
  36. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-10-29 09:47 UTCEchelonGraph re-scored
  38. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  39. 2026-10-28 11:30 UTCEchelonGraph re-scored
  40. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-10-27 04:17 UTCEchelonGraph re-scored
  42. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  43. 2026-10-26 01:37 UTCEchelonGraph re-scored
  44. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  45. 2026-10-25 14:54 UTCEchelonGraph re-scored
  46. 2026-10-25 03:18 UTCEchelonGraph re-scored
  47. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-10-24 05:03 UTCEchelonGraph re-scored
  49. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-10-23 06:46 UTCEchelonGraph re-scored
  51. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-10-22 08:28 UTCEchelonGraph re-scored
  53. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-10-21 10:12 UTCEchelonGraph re-scored
  55. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-10-19 19:12 UTCEchelonGraph re-scored
  57. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  58. 2026-10-18 20:53 UTCEchelonGraph re-scored
  59. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-10-18 05:08 UTCEchelonGraph re-scored
  61. 2026-10-17 22:36 UTCEchelonGraph re-scored
  62. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  63. 2026-10-17 00:19 UTCEchelonGraph re-scored
  64. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-10-15 23:46 UTCEchelonGraph re-scored
  66. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  67. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  68. 2026-10-14 15:25 UTCEchelonGraph re-scored
  69. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  70. 2026-10-12 16:34 UTCEchelonGraph re-scored
  71. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  72. 2026-10-12 15:27 UTCEchelonGraph re-scored
  73. 2026-10-12 14:40 UTCEchelonGraph re-scored
  74. 2026-10-11 20:14 UTCEchelonGraph re-scored
  75. 2026-10-11 17:26 UTCEchelonGraph re-scored

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCmurrez/CVE-2026-106445
    Published Oct 10, 2026

    CVE-2026-106445 — Handlebars 4.0.0–4.7.9 RCE via Function.prototype.constructor bypass (GHSA-p8wg-vrv2-v86f). PoCbit PoC + Docker lab (4.7.9), check/exploit HTTP client, GHSA template chain. Fixed 4.7.10. https://pocbit.org/pocs/cve-2026-106445

    Open source ↗

Frequently asked(5)

What is CVE-2026-106445?
CVE-2026-106445 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 3.0.0 until 4.7.10, Handlebars lookupProperty returns Function.prototype.constructor before applying the prototype-access deny list because constructor is an own property of Function.prototype. When an attacker can…
When was the CVE record for CVE-2026-106445 published?
The CVE record for CVE-2026-106445 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-106445 actively exploited?
CVE-2026-106445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106445?
CVE-2026-106445 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106445?
A fix for CVE-2026-106445 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106445 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-106445

Explore →

Is Your Infrastructure Affected by CVE-2026-106445?

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