<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T07:20:32.920057+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/fkie_cve-2026-106120</id>
    <title>fkie_cve-2026-106120</title>
    <updated>2026-10-08T07:20:33.551745+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.2, enabling ownPropertyOnly does not consistently restrict inherited array indices because negative indexing, .first, .last, the first filter, the last filter, join, reverse, slice, compact, and for-loop iteration can read prototype-provided elements outside readJSProperty(). An attacker who can influence prototype state or inherited array-index data and cause templates to render affected operations can disclose values that ownPropertyOnly is expected to hide. Direct positive indexing and ordinary object prototype reads are blocked, but the alternate array paths remain affected. This issue is fixed in 10.27.2.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-106120"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-fwxr-j5w2-587m</id>
    <title>GHSA-fwxr-j5w2-587m — LiquidJS: ownPropertyOnly bypass for inherited array indices in first/last/join/reverse/slice/compact, `.first`/`.last`…</title>
    <updated>2026-10-08T07:20:33.551865+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: liquidjs</p>
<p>## Summary</p>
<p>LiquidJS’s `ownPropertyOnly` option is intended to prevent templates from reading inherited or prototype properties from scope data. 
With `ownPropertyOnly: true`, direct access such as:</p>
<p>```liquid
{{ a[0] }}
```</p>
<p>correctly blocks an inherited array index. However, the same inherited value is still disclosed through:</p>
<p>```text
.first
.last
negative indexing
for-loop iteration
first
last
join
reverse
slice
compact
```</p>
<p>## Impact</p>
<p>This is an information disclosure issue when an application relies on `ownPropertyOnly: true` to safely render templates over untrusted or prototype-polluted scope data.</p>
<p>Object prototype property reads are blocked as expected, but inherited `Array.prototype` index reads are not consistently blocked. An attacker who can influence prototype state or inherited array-index data may cause templates to disclose values that `ownPropertyOnly` is expected to hide.</p>
<p>## Proof of concept</p>
<p>```js
const { Liquid } = require("liquidjs");</p>
<p>const engine = new Liquid({ ownPropertyOnly: true });</p>
<p>Array.prototype[0] = "ARRAY_PROTO_POLLUTED";
Object.prototype.secret = "OBJECT_PROTO_POLLUTED";</p>
<p>const a = [];
a.length = 1;</p>
<p>const o = {};</p>
<p>for (const [src, scope] of [
  ["{{ a[0] }}", { a }],
  ["{{ a[-1] }}", { a }],
  ["{{ o.secret }}", { o }],
  ["{{ a.first }}", { a }],
  ["{{ a.last }}", { a }],
  ["{{ a | first }}", { a }],
  ["{{ a | last }}", { a }],
  ["{{ a | join: ',' }}", { a }],
  ["{{ a | reverse | first }}", { a }],
  ["{{ a | slice: 0, 1 | join:…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-fwxr-j5w2-587m"/>
  </entry>
</feed>
