Vulnerability Database · npm · liquidjs · Version

liquidjs 10.22.0

10.22.0 is affected by 17 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 10.30.0.

Critical 1 High 9 Medium 6 Low 1 Unrated 0

Released 06 Oct 2025 Licence MIT Also known from other sources 17 Newer releases 235 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

liquidjs 10.22.0 vulnerabilities

17 vulnerabilities cover liquidjs 10.22.0. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2026-45618: LiquidJS Remote Code Execution Vulnerability 10.0 critical 10.26.0 27 May 2026
CVE-2026-30952: LiquidJS Path Traversal Vulnerability 8.7 high 10.25.0 10 Mar 2026
CVE-2026-55575: LiquidJS Memory Limit Bypass via Pop Filter 8.2 high 10.27.1 24 Jul 2026
CVE-2026-35525: LiquidJS Symlink Vulnerability Allows Unauthorized File Access 8.2 high 10.25.3 08 Apr 2026
CVE-2026-69222: LiquidJS Uncontrolled Resource Consumption in `join` Filter 7.5 high 10.27.2 08 Sep 2026
CVE-2026-45617: LiquidJS Vulnerable to ReDoS via Quadratic Backtracking in `strip_html` Filter Regex 7.5 high 10.26.0 27 May 2026
CVE-2026-45357: LiquidJS Memory and Render Limit Bypass via Unbounded Width Padding in Date Filter 7.5 high No fix published 27 May 2026
CVE-2026-41311: liquidjs Denial of Service via Circular Block Reference in Layout 7.5 high 10.25.7 24 Apr 2026
CVE-2026-33287: LiquidJS Exponential Memory Amplification Vulnerability in replace_first Filter 7.5 high No fix published 25 Mar 2026
CVE-2026-33285: LiquidJS Memory Limit Bypass Leading to Process Crash 7.5 high No fix published 25 Mar 2026
CVE-2026-44645: LiquidJS Render Limit DoS Guard Bypass via Empty For Loop 6.5 medium No fix published 27 May 2026
CVE-2026-39859: LiquidJS Arbitrary File Read via renderFile() and parseFile() 6.3 medium 10.25.5 08 Apr 2026
CVE-2026-44644: LiquidJS XSS Vulnerability via strip_html Filter Bypass 6.1 medium No fix published 27 May 2026
CVE-2026-106120: LiquidJS Information Disclosure via ownPropertyOnly Bypass 6.0 medium 10.27.2 07 Oct 2026
CVE-2026-44646: LiquidJS's Render Tag Bypasses Security Option Leading to Information Disclosure 5.3 medium No fix published 27 May 2026
CVE-2026-39412: LiquidJS Information Disclosure via sort_natural Filter Bypass 5.3 medium 10.25.4 08 Apr 2026
CVE-2026-34166: LiquidJS Memory Limit Bypass via Quadratic Amplification in `replace` Filter 3.7 low 10.25.3 08 Apr 2026

Looking for another version, or everything Vulert holds for liquidjs?

All versions → Full vulnerability list →

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 →

Questions

About liquidjs 10.22.0

Is liquidjs 10.22.0 vulnerable?

Yes. 17 vulnerabilities in the Vulert database cover liquidjs 10.22.0: 1 critical, 9 high, 6 medium and 1 low. The upgrade Vulert recommends is 10.30.0, and each entry above names the fixed version to move to.

Which version of liquidjs should I use instead of 10.22.0?

10.30.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 10.22.0 the latest release of liquidjs?

No. 10.22.0 was published 06 Oct 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor liquidjs for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the liquidjs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.