Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

LiquidJS has a renderLimit DoS guard bypass via empty {% for %} body

CVE-2026-44645GHSA-8xx9-69p8-7jp3

What to do

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-44645: 0.39% estimated exploitation activity in the next 30 days; percentile 32.65 (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 The `renderLimit` option — documented in `docs/source/tutorials/dos.md` as the mechanism that "mitigates this by limiting the time consumed by each render() call" — can be fully bypassed by a `{% for %}` (or `{% tablerow %}`) tag whose body is empty. The per-iteration time check is reached only when the body contains at least one template node, so a template like `{%- for i in (1..N) -%}{%- endfor -%}` iterates the full collection without ever consulting `renderLimit`. With a configured `renderLimit` of 50 ms, a single `parseAndRenderSync` call has been observed to consume 2.26 seconds (~45× over the limit) and scales linearly with `N` up to `memoryLimit`, allowing a low-privileged template author to wedge an event-loop thread for an attacker-chosen duration.

Details `Render.renderTemplates` is the single point at which `renderLimit` is consulted: ```ts // src/render/render.ts 14: public * renderTemplates (templates: Template[], ctx: Context, emitter?: Emitter):…

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

    Amended from osv record GHSA-8xx9-69p8-7jp3

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-8xx9-69p8-7jp3

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-8xx9-69p8-7jp3

  4. Revision 1 · created ·

    Published from osv record GHSA-8xx9-69p8-7jp3

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

Advisory: LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body
IDs: CVE-2026-44645, GHSA-8xx9-69p8-7jp3
Record: https://patchnext.com/advisories/cve-2026-44645 (revision 4, source checked 28 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.26.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm liquidjs: affected < 10.26.0; fixed in 10.26.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-8xx9-69p8-7jp3 (OSV record GHSA-8xx9-69p8-7jp3 lists affected ranges: npm liquidjs >=0 <=10.25.7)
- Verified: https://github.com/advisories/GHSA-8xx9-69p8-7jp3 (GitHub-reviewed advisory GHSA-8xx9-69p8-7jp3 lists affected ranges: npm liquidjs >=0 <=10.25.7)
- Verified: https://github.com/advisories/GHSA-8xx9-69p8-7jp3 (GitHub-reviewed advisory GHSA-8xx9-69p8-7jp3 lists affected ranges: npm liquidjs >=0 <10.26.0)
- Verified: https://osv.dev/vulnerability/GHSA-8xx9-69p8-7jp3 (OSV record GHSA-8xx9-69p8-7jp3 lists affected ranges: npm liquidjs >=0 <10.26.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…