liquidjs has a path traversal fallback vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-30952: 0.58% estimated exploitation activity in the next 30 days; percentile 47.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The layout, render, and include tags allow arbitrary file access via absolute paths (either as string literals or through Liquid variables, the latter require dynamicPartials: true, which is the default). This poses a security risk when malicious users are allowed to control the template content or specify the filepath to be included as a Liquid variable. Patches The root cause is LiquidJS allows require.resolve() as fallback but doesn't limit the directories it can resolve to. The issue is fixed via #855 and published version 10.25.0 on npm. Workarounds Change the files in build time In build time, through Shell script or Webpack string-replace-loader, change the file content of correxponding file (depending on your package type, for CommonJS it's dist/liquid.node.js) under dist/, Overriding by fs LiquidJS option Adding a fs option to override the default fs implementation: References Discussions: https://github.com/harttle/liquidjs/pull/851 Code fix:…

Published by the source

10 Mar 2026, 01:04 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wmfp-5q7x-987x

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wmfp-5q7x-987x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30952

Advisory: liquidjs has a path traversal fallback vulnerability
IDs: CVE-2026-30952, GHSA-wmfp-5q7x-987x
Record: https://patchnext.com/advisories/cve-2026-30952 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: liquidjs 10.25.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm liquidjs: affected < 10.25.0; fixed in 10.25.0

## Suggested inspection (read-only)
- `npm ls liquidjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on liquidjs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wmfp-5q7x-987x (OSV record GHSA-wmfp-5q7x-987x lists affected ranges: npm liquidjs >=0 <10.25.0 (fixed))
- Verified: https://github.com/advisories/GHSA-wmfp-5q7x-987x (GitHub-reviewed advisory GHSA-wmfp-5q7x-987x lists affected ranges: npm liquidjs >=0 <10.25.0)

Commands are suggestions: review each one before running it.