CVE-2026-106120: LiquidJS Information Disclosure via ownPropertyOnly Bypass

liquidjs Updated 07 Oct 2026

Summary

07/10/2026
Yes i
Moderate
6.0

CVE-2026-106120: LiquidJS’s ownPropertyOnly option is intended to prevent templates from reading inherited or prototype properties from scope data. Affects liquidjs versions < 10.27.2. Fixed in 10.27.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

LiquidJS is a powerful templating engine for JavaScript that allows developers to create dynamic web applications by rendering templates with data. It supports various features such as filters, loops, and custom tags, making it a versatile choice for developers. However, it has a vulnerability related to its 'ownPropertyOnly' option, which is designed to prevent access to inherited properties in scope data.

Vulnerability Detail

The vulnerability arises from LiquidJS's 'ownPropertyOnly' option, which is intended to block access to inherited or prototype properties. While direct access to properties like 'a[0]' is correctly restricted, inherited array indices can still be accessed through methods such as '.first', '.last', negative indexing, and for-loop iterations. This inconsistency can lead to information disclosure when applications rely on 'ownPropertyOnly: true' to secure templates against untrusted data. An attacker can exploit this flaw by manipulating prototype states to expose sensitive information.

How To Fix

Latest published version: 10.30.0 as of 22 Oct 2026

npm install liquidjs@10.30.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

10.27.2

This is the first release that contains the fix.

npm install liquidjs@10.27.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid using the 'ownPropertyOnly' option if your application processes untrusted data. Additionally, ensure that your application does not allow prototype pollution, which can be done by validating and sanitizing input data.

Conclusion

In summary, CVE-2026-106120 is a vulnerability in LiquidJS that allows for information disclosure through inherited array indices despite the 'ownPropertyOnly' option being enabled. It is crucial for developers to update to the latest version to mitigate this risk and ensure the security of their applications.

See every vulnerability recorded for liquidjs →

Share this vulnerability

FAQ

The vulnerability can lead to information disclosure, allowing attackers to access inherited properties that should be restricted.

You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to receive real-time alerts.

The CVSS score for this vulnerability is 6.0, indicating a moderate severity level.

While updating is the best solution, you can temporarily avoid using the 'ownPropertyOnly' option and sanitize input data.

You can find more information about LiquidJS and its features on its official GitHub repository.

Related vulnerabilities

Recent vulnerabilities recorded for liquidjs.

How To Fix

Latest published version: 10.30.0 as of 22 Oct 2026

npm install liquidjs@10.30.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

10.27.2

This is the first release that contains the fix.

npm install liquidjs@10.27.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback