Skip to content
Web

CVE-2026-45618

CRITICAL
Critical
EPSS 0.92%Patch availableAug 12, 2026

Remote code execution in LiquidJS templates (pre-10.26.0).

common questions

Is CVE-2026-45618 being exploited?

Not confirmed. CVE-2026-45618 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.92% probability of exploitation in the next 30 days.

How severe is CVE-2026-45618?

CVE-2026-45618 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-45618?

Yes. A fix has been recorded for CVE-2026-45618. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-45618 affect?

CVE-2026-45618 affects LiquidJS < 10.26.0, Web applications using LiquidJS templates, GitHub Pages/Shopify integrations using LiquidJS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-45618?

Upgrade LiquidJS to >=10.26.0; audit templates, rotate credentials, review logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LiquidJS < 10.26.0Web applications using LiquidJS templatesGitHub Pages/Shopify integrations using LiquidJS
impact

Remote code execution via crafted templates, enabling arbitrary code execution in server process, data theft, or full app takeover.

action required

Immediate action required

affected versions
harttle liquidjs
  • affected< 10.26.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free