<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-18T04:11:07.518399+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-161218</id>
    <title>EUVD-2026-161218</title>
    <updated>2026-10-18T04:11:07.520685+00:00</updated>
    <content>EUVD-2026-161218</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-161218"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-45390</id>
    <title>fkie_cve-2024-45390</title>
    <updated>2026-10-18T04:11:07.520718+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>@blakeembrey/template is a string template library. Prior to version 1.2.0, it is possible to inject and run code within the template if the attacker has access to write the template name. Version 1.2.0 contains a patch. As a workaround, don't pass untrusted input as the template display name, or don't use the display name feature.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-45390"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q765-wm9j-66qj</id>
    <title>GHSA-q765-wm9j-66qj — @blakeembrey/template vulnerable to code injection when attacker controls template input</title>
    <updated>2026-10-18T04:11:07.520751+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @blakeembrey/template</p>
<p>### Impact</p>
<p>It is possible to inject and run code within the template if the attacker has access to write the template name.</p>
<p>```js
const { template } = require('@blakeembrey/template');</p>
<p>template("Hello {{name}}!", "exploit() {} &amp;&amp; ((()=&gt;{ console.log('success'); })()) &amp;&amp; function pwned");
```</p>
<p>### Patches</p>
<p>Upgrade to 1.2.0.</p>
<p>### Workarounds</p>
<p>Don't pass untrusted input as the template display name, or don't use the display name feature.</p>
<p>### References</p>
<p>Fixed by removing in https://github.com/blakeembrey/js-template/commit/b8d9aa999e464816c6cfb14acd1ad0f5d1e335aa.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q765-wm9j-66qj"/>
  </entry>
</feed>
