<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 15:22:32 +0000</lastBuildDate>
    <item>
      <title>GHSA-9cx6-37pm-9jff — Handlebars.js has Denial of Service via Malformed Decorator Syntax in Template Compilation</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-9cx6-37pm-9jff</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: handlebars&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a Handlebars template contains decorator syntax referencing an unregistered decorator (e.g. `{{*n}}`), the compiled template calls `lookupProperty(decorators, &amp;#34;n&amp;#34;)`, which returns `undefined`. The runtime then immediately invokes the result as a function, causing an unhandled `TypeError: ... is not a function` that crashes the Node.js process. Any application that compiles user-supplied templates without wrapping the call in a `try/catch` is vulnerable to a single-request Denial of Service.&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;In `lib/handlebars/compiler/javascript-compiler.js`, the code generated for a decorator invocation looks like:&lt;/p&gt;
&lt;p&gt;```javascript
fn = lookupProperty(decorators, &amp;#34;n&amp;#34;)(fn, props, container, options) || fn;
```&lt;/p&gt;
&lt;p&gt;When `&amp;#34;n&amp;#34;` is not a registered decorator, `lookupProperty(decorators, &amp;#34;n&amp;#34;)` returns `undefined`. The expression immediately attempts to call `undefined` as a function, producing:&lt;/p&gt;
&lt;p&gt;```
TypeError: lookupProperty(...) is not a function
```&lt;/p&gt;
&lt;p&gt;Because the error is thrown inside the compiled template function and is not caught by the runtime, it propagates up as an unhandled exception and — when not caught by the application — crashes the Node.js process.&lt;/p&gt;
&lt;p&gt;This inconsistency is notable: references to unregistered **helpers** produce a clean `&amp;#34;Missing helper: ...&amp;#34;` error, while references to unregistered **decorators** cause a hard crash.&lt;/p&gt;
&lt;p&gt;**Attack scenario:** An attacker submits `{{*n}}` as template content to any endpoint that calls `Handlebars.compile(userIn…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: handlebars&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a Handlebars template contains decorator syntax referencing an unregistered decorator (e.g. `{{*n}}`), the compiled template calls `lookupProperty(decorators, &amp;#34;n&amp;#34;)`, which returns `undefined`. The runtime then immediately invokes the result as a function, causing an unhandled `TypeError: ... is not a function` that crashes the Node.js process. Any application that compiles user-supplied templates without wrapping the call in a `try/catch` is vulnerable to a single-request Denial of Service.&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;In `lib/handlebars/compiler/javascript-compiler.js`, the code generated for a decorator invocation looks like:&lt;/p&gt;
&lt;p&gt;```javascript
fn = lookupProperty(decorators, &amp;#34;n&amp;#34;)(fn, props, container, options) || fn;
```&lt;/p&gt;
&lt;p&gt;When `&amp;#34;n&amp;#34;` is not a registered decorator, `lookupProperty(decorators, &amp;#34;n&amp;#34;)` returns `undefined`. The expression immediately attempts to call `undefined` as a function, producing:&lt;/p&gt;
&lt;p&gt;```
TypeError: lookupProperty(...) is not a function
```&lt;/p&gt;
&lt;p&gt;Because the error is thrown inside the compiled template function and is not caught by the runtime, it propagates up as an unhandled exception and — when not caught by the application — crashes the Node.js process.&lt;/p&gt;
&lt;p&gt;This inconsistency is notable: references to unregistered **helpers** produce a clean `&amp;#34;Missing helper: ...&amp;#34;` error, while references to unregistered **decorators** cause a hard crash.&lt;/p&gt;
&lt;p&gt;**Attack scenario:** An attacker submits `{{*n}}` as template content to any endpoint that calls `Handlebars.compile(userIn…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-9cx6-37pm-9jff</guid>
    </item>
  </channel>
</rss>
