<?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>Wed, 07 Oct 2026 13:24:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-328471</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328471</link>
      <description>EUVD-2026-328471</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328471</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45357</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45357</link>
      <description>&lt;p&gt;LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the date filter&amp;#39;s strftime implementation parses width specifiers like %9999999d and forwards the captured width unchecked into pad()/padStart(), leading to memory and render limit bypass. In src/util/underscore.ts, the pad loop performs unbounded string concatenation without consulting the Context&amp;#39;s memoryLimit or renderLimit, so a single small template ({{ x | date: &amp;#39;%5000000d&amp;#39; }}) produces megabytes of output and unbounded CPU. The memoryLimit and renderLimit options the docs (src/liquid-options.ts:87-92) advertise as DoS controls — and which the docstring explicitly mentions for strftime — are entirely bypassed. Exploitation can cause large memory allocations, high CPU usage, or OOM crashes per render. 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. In versions 10.25.7 and below, the date filter&amp;#39;s strftime implementation parses width specifiers like %9999999d and forwards the captured width unchecked into pad()/padStart(), leading to memory and render limit bypass. In src/util/underscore.ts, the pad loop performs unbounded string concatenation without consulting the Context&amp;#39;s memoryLimit or renderLimit, so a single small template ({{ x | date: &amp;#39;%5000000d&amp;#39; }}) produces megabytes of output and unbounded CPU. The memoryLimit and renderLimit options the docs (src/liquid-options.ts:87-92) advertise as DoS controls — and which the docstring explicitly mentions for strftime — are entirely bypassed. Exploitation can cause large memory allocations, high CPU usage, or OOM crashes per render. 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-45357</guid>
    </item>
    <item>
      <title>GHSA-hh27-hf48-9f5q — LiquidJS has a memory and render limit bypass via unbounded width padding in `date` filter (strftime)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hh27-hf48-9f5q</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 `date` filter&amp;#39;s strftime implementation parses width specifiers like `%9999999d` and forwards the captured width unchecked into `pad()`/`padStart()` in `src/util/underscore.ts`. The pad loop performs unbounded string concatenation without consulting the Context&amp;#39;s `memoryLimit` or `renderLimit`, so a single small template (`{{ x | date: &amp;#39;%5000000d&amp;#39; }}`) produces megabytes of output and unbounded CPU. The `memoryLimit` and `renderLimit` options the docs (`src/liquid-options.ts:87-92`) advertise as DoS controls — and which the docstring explicitly mentions for `strftime` — are entirely bypassed.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`date.ts:5-13` only charges `memoryLimit` for the lengths of the input value, format string, and timezone:&lt;/p&gt;
&lt;p&gt;```ts
export function date (this: FilterImpl, v: string | Date, format?: string, timezoneOffset?: number | string) {
  const size = ((v as string)?.length ?? 0) + (format?.length ?? 0) + ((timezoneOffset as string)?.length ?? 0)
  this.context.memoryLimit.use(size)
  ...
  return strftime(date, format)
}
```&lt;/p&gt;
&lt;p&gt;`strftime` (`src/util/strftime.ts:121`) then walks the format with `rFormat = /%([-_0^#:]+)?(\d+)?([EO])?(.)/`. The captured `width` group is passed directly to `padStart`:&lt;/p&gt;
&lt;p&gt;```ts
function format (d, match) {
  const [input, flagStr = &amp;#39;&amp;#39;, width, modifier, conversion] = match
  ...
  let padWidth = width || padWidths[conversion] || 0
  ...
  return padStart(ret, padWidth, padChar)   // strftime.ts:147
}
```&lt;/p&gt;
&lt;p&gt;`padStart` calls `pad()` in `src/util/un…&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 `date` filter&amp;#39;s strftime implementation parses width specifiers like `%9999999d` and forwards the captured width unchecked into `pad()`/`padStart()` in `src/util/underscore.ts`. The pad loop performs unbounded string concatenation without consulting the Context&amp;#39;s `memoryLimit` or `renderLimit`, so a single small template (`{{ x | date: &amp;#39;%5000000d&amp;#39; }}`) produces megabytes of output and unbounded CPU. The `memoryLimit` and `renderLimit` options the docs (`src/liquid-options.ts:87-92`) advertise as DoS controls — and which the docstring explicitly mentions for `strftime` — are entirely bypassed.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`date.ts:5-13` only charges `memoryLimit` for the lengths of the input value, format string, and timezone:&lt;/p&gt;
&lt;p&gt;```ts
export function date (this: FilterImpl, v: string | Date, format?: string, timezoneOffset?: number | string) {
  const size = ((v as string)?.length ?? 0) + (format?.length ?? 0) + ((timezoneOffset as string)?.length ?? 0)
  this.context.memoryLimit.use(size)
  ...
  return strftime(date, format)
}
```&lt;/p&gt;
&lt;p&gt;`strftime` (`src/util/strftime.ts:121`) then walks the format with `rFormat = /%([-_0^#:]+)?(\d+)?([EO])?(.)/`. The captured `width` group is passed directly to `padStart`:&lt;/p&gt;
&lt;p&gt;```ts
function format (d, match) {
  const [input, flagStr = &amp;#39;&amp;#39;, width, modifier, conversion] = match
  ...
  let padWidth = width || padWidths[conversion] || 0
  ...
  return padStart(ret, padWidth, padChar)   // strftime.ts:147
}
```&lt;/p&gt;
&lt;p&gt;`padStart` calls `pad()` in `src/util/un…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hh27-hf48-9f5q</guid>
    </item>
  </channel>
</rss>
