CVE-2026-45618: LiquidJS is Vulnerable to Remote Code Execution
LiquidJS is a Shopify/GitHub Pages compatible template engine. Prior to version 10.26.0, it is possible to execute arbitrary code with crafted templates. Version 10.26.0 patches the issue.
Security readout for executives and security teams
Plain-English summary
LiquidJS versions before 10.26.0 can allow a crafted template to run arbitrary code. If an application lets untrusted users supply or influence templates, an attacker could potentially compromise the service and its accessible data or systems. Version 10.26.0 addresses the vulnerability.
Executive priority
Treat this as an immediate remediation priority where untrusted templates reach affected LiquidJS versions. Confirm exposure quickly, upgrade exposed production systems, and assess whether potentially vulnerable rendering services handled attacker-controlled input.
Technical view
CVE-2026-45618 is a CWE-94 code-injection vulnerability in LiquidJS before 10.26.0. Crafted templates may execute arbitrary code. The CVSS 3.1 score is 10.0, describing network-reachable, low-complexity, unauthenticated exploitation without user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure requires LiquidJS earlier than 10.26.0 and a path through which an attacker can supply or meaningfully influence templates. Internet-facing template editors, rendering APIs, or stored user-controlled templates deserve immediate review. The supplied evidence does not identify specific affected deployments.
Exploitation context
The supplied sources establish arbitrary code execution from crafted templates but provide no evidence of active exploitation. This CVE is not listed as KEV in the bundle. Absence from KEV does not prove exploitation is not occurring.
Researcher notes
The public bundle attributes the flaw to crafted-template code execution and identifies 10.26.0 as patched. It does not provide enough detail to characterize the vulnerable code path, required template features, sandbox boundaries, exploit reliability, or observed attacks. Validate reachability without attempting weaponization.
Mitigation direction
Upgrade LiquidJS to version 10.26.0 or later.
Prioritize systems that render externally supplied or user-influenced templates.
Until upgraded, prevent untrusted parties from supplying or modifying templates.
Review the vendor advisory and release notes for deployment-specific guidance.
Validation and detection
Identify direct and transitive LiquidJS versions in manifests, lockfiles, SBOMs, and deployed artifacts.
Confirm each running environment uses LiquidJS 10.26.0 or later.
Map every template source and determine whether untrusted users can influence it.
Run existing rendering and security regression tests after upgrading.
Review relevant application telemetry for suspicious template-processing activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.