# CVE-2026-39412: LiquidJS: ownPropertyOnly bypass via sort_natural filter — prototype property information disclosure through sorting side-channel

> Attackers can extract sensitive prototype properties like API keys via a sorting side-channel in LiquidJS when ownPropertyOnly is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-rv5g-f82m-qrvv, MINI-f69w-8762-mh4c, MINI-mmgq-73gf-hf4r

## What is CVE-2026-39412?

CVE-2026-39412 is a medium-severity vulnerability in harttle liquidjs, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.4, the sort_natural filter bypasses the ownPropertyOnly security option, allowing template authors to extract values of prototype-inherited properties through a sorting side-channel attack. Applications relying on ownPropertyOnly: true as a security boundary (e.g., multi-tenant template systems) are exposed to information disclosure of sensitive prototype properties such as API keys and tokens. This vulnerability is fixed in 10.25.4.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-39412?

2 open source packages ship an affected version, including liquidjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `liquidjs` | npm | All versions | 10.25.4 |
| `liquidjs` | npm | All versions | 10.25.4 |

Products: Liquidjs Liquidjs.

## How do I fix CVE-2026-39412?

Upgrade liquidjs to 10.25.4 or later.

## Is CVE-2026-39412 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39412 exists.

## Other vulnerabilities in harttle liquidjs

- [CVE-2026-30952](https://insights.sbomify.com/CVE-2026-30952/): liquidjs has a path traversal fallback vulnerability (high 8.7)
- [CVE-2026-35525](https://insights.sbomify.com/CVE-2026-35525/): LiquidJS has a root restriction bypass for partial and layout loading through symlinked templates (high 8.2)
- [CVE-2026-41311](https://insights.sbomify.com/CVE-2026-41311/): LiquidJS is vulnerable to Denial of Service via circular block reference in layout (high 7.5)
- [CVE-2026-33285](https://insights.sbomify.com/CVE-2026-33285/): LiquidJS: memoryLimit Bypass through Negative Range Values Leads to Process Crash (high 7.5)
- [CVE-2026-33287](https://insights.sbomify.com/CVE-2026-33287/): LiquidJS has Exponential Memory Amplification through its replace_first Filter $& Pattern (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39412 and fix it if it is affected.

What it is: CVE-2026-39412 is a medium-severity vulnerability in harttle liquidjs, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39412 exists.

Affected packages and fixed versions:
- liquidjs (npm): affected all versions; fixed in 10.25.4
- liquidjs (npm): affected all versions; fixed in 10.25.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39412/ (Markdown: https://insights.sbomify.com/CVE-2026-39412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39412
- OSV: https://osv.dev/vulnerability/CVE-2026-39412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39412/
Summaries are generated and may contain mistakes; the official description above is the record.