CVE-2026-106446

validatedZero produced an exploit or a check.

GHSA-8r5x-fm3f-whwj ↗EUVD-2026-93969 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.9dkevAttacks confirmed in the real world.
handlebars-lang handlebars.js >= 4.0.0, <= 4.7.9
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-803, permanent identifier
pkg:npm/handlebars
+8h48mTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal −0.9dcve.org publicationcheck available+0.4dagent stoppedpublic poc+1.9d
0
+1d

description

Handlebars before 4.7.10 can generate attacker-controlled JavaScript when an application passes an untrusted object to compile() or precompile() instead of a template string. This can execute code in the server process during rendering or in environments that load generated precompiled templates. Applications that pass only template strings are not affected.

mitigation

Upgrade the npm handlebars package to version 4.7.10 or later. Ensure inputs to compile() and precompile() are strings, and use the runtime-only build on servers that compile templates only during builds.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.64%49th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 19:41Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1.9d
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-05 22:40Z
  2. 2026-10-06 19:41Z
    cve_org: trigger signal, started the run
  3. 2026-10-08 17:52Z

this entry in the feed

GET /api/v1/feed/CVE-2026-106446

{
  "etk_id": "ETK-2026-803",
  "cve_id": "CVE-2026-106446",
  "display_id": "CVE-2026-106446",
  "ghsa_id": "GHSA-8r5x-fm3f-whwj",
  "euvd_id": "EUVD-2026-93969",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code injection through untrusted ASTs in Handlebars",
  "summary": "Handlebars before 4.7.10 can generate attacker-controlled JavaScript when an application passes an untrusted object to compile() or precompile() instead of a template string. This can execute code in the server process during rendering or in environments that load generated precompiled templates. Applications that pass only template strings are not affected.",
  "mitigation": "Upgrade the npm handlebars package to version 4.7.10 or later. Ensure inputs to compile() and precompile() are strings, and use the runtime-only build on servers that compile templates only during builds.",
  "vendor": "handlebars-lang",
  "product": "handlebars.js",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, <= 4.7.9"
      ],
      "ecosystem": "npm",
      "fixed_versions": [],
      "package_name": "handlebars",
      "purl": "pkg:npm/handlebars"
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0064,
  "epss_percentile": 0.4977,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 13.718564116666666,
  "t0_at": "2026-10-06T19:41:55.785000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T04:30:19.791456+00:00",
      "days": 0.36694451916666665,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T19:41:55.785000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-08T17:52:32+00:00",
      "days": 1.9240302662037037,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T19:41:55.785000+00:00",
      "url": "https://github.com/advisories/GHSA-8r5x-fm3f-whwj"
    },
    "trigger_signal": {
      "at": "2026-10-05T22:40:54+00:00",
      "days": -0.8757151041666666,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T19:41:55.785000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106446"
    }
  }
}

published 2026-10-06 20:01Z
last change 2026-10-21 14:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.