Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

LiquidJS: Root restriction bypass for partial and layout loading through symlinked templates

CVE-2026-35525GHSA-56p5-8mhr-2fph

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (liquidjs 10.25.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm liquidjs

    Affected
    <= 10.25.2
    Fixed in
    10.25.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-35525: 0.40% estimated exploitation activity in the next 30 days; percentile 33.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary LiquidJS enforces partial and layout root restrictions using the resolved pathname string, but it does not resolve the canonical filesystem path before opening the file. A symlink placed inside an allowed partials or layouts directory can therefore point to a file outside that directory and still be loaded. Details For {% include %}, {% render %}, and {% layout %}, LiquidJS checks whether the candidate path is inside the configured partials or layouts roots before reading it. That check is path-based, not realpath-based. Because of that, a file like partials/link.liquid passes the directory containment check as long as its pathname is under the allowed root. If link.liquid is actually a symlink to a file outside the allowed root, the filesystem follows the symlink when the file is opened and LiquidJS renders the external target. So the restriction is applied to the path string that was requested, not to the file that is actually read. This matters in environments where an…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-56p5-8mhr-2fph

  2. Revision 2 · amended ·

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

  3. Revision 1 · created ·

    Published from osv record GHSA-56p5-8mhr-2fph

Agent brief

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

# Patch Next advisory brief: CVE-2026-35525

Advisory: LiquidJS: Root restriction bypass for partial and layout loading through symlinked templates
IDs: CVE-2026-35525, GHSA-56p5-8mhr-2fph
Record: https://patchnext.com/advisories/cve-2026-35525 (revision 3, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
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.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm liquidjs: affected <= 10.25.2; fixed in 10.25.3

## 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-56p5-8mhr-2fph (OSV record GHSA-56p5-8mhr-2fph lists affected ranges: npm liquidjs >=0 <10.25.3 (fixed))
- Verified: https://github.com/advisories/GHSA-56p5-8mhr-2fph (GitHub-reviewed advisory GHSA-56p5-8mhr-2fph lists affected ranges: npm liquidjs >=0 <=10.25.2)

Commands are suggestions: review each one before running it.

Loading voting…