# LiquidJS's \`{% render %}\` tag silently bypasses per-render \`ownPropertyOnly:true\` via \`Context.spawn()\`

Advisory record · `GHSA-9x9p-qf8f-mvjg`

- **Identifiers:** `GHSA-9x9p-qf8f-mvjg` · `CVE-2026-44646`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 27 May 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 May 2026, 00:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `liquidjs` (npm): affected `<10.26.0`; fixed in `10.26.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Liquidjs versions before 10.26.0 are affected: when a template uses the {% render %} tag, the per-render ownPropertyOnly:true override passed to parseAndRender() is dropped inside the partial, so prototype-chain properties of objects can still be read from within the partial. An attacker who can supply template content rendered through {% render %} (for example CMS snippets or theme partials) could read such properties, possibly including sensitive values. Upgrade liquidjs to version 10.26.0 or later, which contains the fix.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 26th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9x9p-qf8f-mvjg)

## Sources

- [GitHub Advisory Database: GHSA-9x9p-qf8f-mvjg](https://github.com/advisories/GHSA-9x9p-qf8f-mvjg)
- [OSV: GHSA-9x9p-qf8f-mvjg](https://osv.dev/vulnerability/GHSA-9x9p-qf8f-mvjg)
- <https://github.com/harttle/liquidjs/security/advisories/GHSA-9x9p-qf8f-mvjg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44646>
- <https://github.com/harttle/liquidjs/commit/dbbf6288030591bf6da28d8c1cce5a17bca97bb6>
- <https://github.com/harttle/liquidjs>
- <https://github.com/harttle/liquidjs/blob/v10.26.0/CHANGELOG.md>
- <https://github.com/harttle/liquidjs/releases/tag/v10.26.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9x9p-qf8f-mvjg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9x9p-qf8f-mvjg/>. Everything for agents: <https://agentprime.io/llms.txt>.