Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

liquidjs has a Denial of Service via circular block reference in layout

CVE-2026-41311GHSA-4rc3-7j7w-m548

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (liquidjs 10.25.7), 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.7
    Fixed in
    10.25.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-41311: 0.38% estimated exploitation activity in the next 30 days; percentile 32.35 (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 A circular block reference in {% layout %} / {% block %} causes an infinite recursive loop, consuming all available memory (~4GB) and crashing the Node.js process with FATAL ERROR: JavaScript heap out of memory. This allows any user who can submit a Liquid template to perform a Denial of Service attack. Details In src/tags/block.ts, during OUTPUT mode, each block looks up its render function from ctx.getRegister('blocks')[this.block]. When a block with name a is nested inside another block also named a in a child template, the inner block finds the outer block's render function and calls it. The outer block's templates contain the inner block again, creating infinite recursion with no termination condition. Relevant code (src/tags/block.ts, getBlockRender method): When renderChild exists (same-name block found), it calls renderChild which re-renders templates containing the nested block, which again finds renderChild, and so on — infinite loop. PoC 1. Create a layout file…

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

    Amended from ghsa record GHSA-4rc3-7j7w-m548

  2. Revision 1 · created ·

    Published from osv record GHSA-4rc3-7j7w-m548

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-41311

Advisory: liquidjs has a Denial of Service via circular block reference in layout
IDs: CVE-2026-41311, GHSA-4rc3-7j7w-m548
Record: https://patchnext.com/advisories/cve-2026-41311 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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.7. A vendor fix does not mean a deployment is fixed.

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

## 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-4rc3-7j7w-m548 (OSV record GHSA-4rc3-7j7w-m548 lists affected ranges: npm liquidjs >=0 <10.25.7 (fixed))
- Verified: https://github.com/advisories/GHSA-4rc3-7j7w-m548 (GitHub-reviewed advisory GHSA-4rc3-7j7w-m548 lists affected ranges: npm liquidjs >=0 <10.25.7)

Commands are suggestions: review each one before running it.

Loading voting…