<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 19:03:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-328491</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328491</link>
      <description>EUVD-2026-328491</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328491</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44644</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44644</link>
      <description>&lt;p&gt;LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. Versions 10.25.7 and below are vulnerable to XSS through a flaw in the strip_html filter logic. The strip_html filter is intended to remove HTML tags from a string before rendering, and is widely used as an XSS sanitizer. The implementation uses a regex whose catch-all branch (&amp;lt;.*?&amp;gt;) does not match line terminators, so any HTML tag containing a \n or \r character passes through unmodified. An attacker who can place a newline inside a tag (e.g. &amp;lt;img\nsrc=x\nonerror=alert(1)&amp;gt;) bypasses sanitization entirely, since browsers treat newlines as whitespace within a tag and execute the resulting onerror/onload/etc. handler. Exploitation is possible for applications that both render attacker-controlled strings via {{ x | strip_html }} to defend against HTML injection and do not separately HTML-escape that output (default behavior — outputEscape is unset by default). This issue has been fixed in version 10.26.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. Versions 10.25.7 and below are vulnerable to XSS through a flaw in the strip_html filter logic. The strip_html filter is intended to remove HTML tags from a string before rendering, and is widely used as an XSS sanitizer. The implementation uses a regex whose catch-all branch (&amp;lt;.*?&amp;gt;) does not match line terminators, so any HTML tag containing a \n or \r character passes through unmodified. An attacker who can place a newline inside a tag (e.g. &amp;lt;img\nsrc=x\nonerror=alert(1)&amp;gt;) bypasses sanitization entirely, since browsers treat newlines as whitespace within a tag and execute the resulting onerror/onload/etc. handler. Exploitation is possible for applications that both render attacker-controlled strings via {{ x | strip_html }} to defend against HTML injection and do not separately HTML-escape that output (default behavior — outputEscape is unset by default). This issue has been fixed in version 10.26.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44644</guid>
    </item>
    <item>
      <title>GHSA-2qv6-9wx5-cwv4 — LiquidJS's strip_html filter bypass via newline characters in HTML tags enables XSS</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2qv6-9wx5-cwv4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: liquidjs&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `strip_html` filter in liquidjs is intended to remove HTML tags from a string before rendering, and is widely used as an XSS sanitizer. The implementation uses a regex whose catch-all branch (`&amp;lt;.*?&amp;gt;`) does not match line terminators, so any HTML tag containing a `\n` or `\r` character passes through unmodified. An attacker who can place a newline inside a tag (e.g. `&amp;lt;img\nsrc=x\nonerror=alert(1)&amp;gt;`) bypasses sanitization entirely, since browsers treat newlines as whitespace within a tag and execute the resulting `onerror`/`onload`/etc. handler. This results in stored or reflected XSS in any application that relies on `strip_html` to neutralize untrusted HTML.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerable code is in `src/filters/html.ts`:&lt;/p&gt;
&lt;p&gt;```ts
// src/filters/html.ts:45-49
export function strip_html (this: FilterImpl, v: string) {
  const str = stringify(v)
  this.context.memoryLimit.use(str.length)
  return str.replace(/&amp;lt;script[\s\S]*?&amp;lt;\/script&amp;gt;|&amp;lt;style[\s\S]*?&amp;lt;\/style&amp;gt;|&amp;lt;.*?&amp;gt;|&amp;lt;!--[\s\S]*?--&amp;gt;/g, &amp;#39;&amp;#39;)
}
```&lt;/p&gt;
&lt;p&gt;The regex has four alternations:
1. `&amp;lt;script[\s\S]*?&amp;lt;\/script&amp;gt;` — uses `[\s\S]`, matches across newlines.
2. `&amp;lt;style[\s\S]*?&amp;lt;\/style&amp;gt;` — uses `[\s\S]`, matches across newlines.
3. `&amp;lt;.*?&amp;gt;` — uses `.`, which in JavaScript does **not** match `\n` or `\r` (no `s`/dotAll flag set).
4. `&amp;lt;!--[\s\S]*?--&amp;gt;` — uses `[\s\S]`, matches across newlines.&lt;/p&gt;
&lt;p&gt;Branch 3 is the catch-all for &amp;#34;any other tag.&amp;#34; Because `.` excludes line terminators, a tag containing a newline does not match any alterna…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: liquidjs&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `strip_html` filter in liquidjs is intended to remove HTML tags from a string before rendering, and is widely used as an XSS sanitizer. The implementation uses a regex whose catch-all branch (`&amp;lt;.*?&amp;gt;`) does not match line terminators, so any HTML tag containing a `\n` or `\r` character passes through unmodified. An attacker who can place a newline inside a tag (e.g. `&amp;lt;img\nsrc=x\nonerror=alert(1)&amp;gt;`) bypasses sanitization entirely, since browsers treat newlines as whitespace within a tag and execute the resulting `onerror`/`onload`/etc. handler. This results in stored or reflected XSS in any application that relies on `strip_html` to neutralize untrusted HTML.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerable code is in `src/filters/html.ts`:&lt;/p&gt;
&lt;p&gt;```ts
// src/filters/html.ts:45-49
export function strip_html (this: FilterImpl, v: string) {
  const str = stringify(v)
  this.context.memoryLimit.use(str.length)
  return str.replace(/&amp;lt;script[\s\S]*?&amp;lt;\/script&amp;gt;|&amp;lt;style[\s\S]*?&amp;lt;\/style&amp;gt;|&amp;lt;.*?&amp;gt;|&amp;lt;!--[\s\S]*?--&amp;gt;/g, &amp;#39;&amp;#39;)
}
```&lt;/p&gt;
&lt;p&gt;The regex has four alternations:
1. `&amp;lt;script[\s\S]*?&amp;lt;\/script&amp;gt;` — uses `[\s\S]`, matches across newlines.
2. `&amp;lt;style[\s\S]*?&amp;lt;\/style&amp;gt;` — uses `[\s\S]`, matches across newlines.
3. `&amp;lt;.*?&amp;gt;` — uses `.`, which in JavaScript does **not** match `\n` or `\r` (no `s`/dotAll flag set).
4. `&amp;lt;!--[\s\S]*?--&amp;gt;` — uses `[\s\S]`, matches across newlines.&lt;/p&gt;
&lt;p&gt;Branch 3 is the catch-all for &amp;#34;any other tag.&amp;#34; Because `.` excludes line terminators, a tag containing a newline does not match any alterna…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2qv6-9wx5-cwv4</guid>
    </item>
  </channel>
</rss>
