VulnerabilityPublished 27 May 2026Updated 28 Oct 2026

CVE-2026-45357: LiquidJS has a memory and render limit bypass via unbounded width padding in `date` filter (strftime)

Affects liquidjsSource GCVE Database

Authoritative record:CVE-2026-45357· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 10.26.0 soon.

Data as of 28 Oct 2026, 17:11 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.26.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade liquidjs to 10.26.0.

Affected software

Product	Affected	Fixed in
npmliquidjs	Affected <10.26.0	Fixed in 10.26.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in LiquidJS version 10.26.0. Operators should upgrade to this version to address the vulnerability. The fix includes capping the padding width in the strftime implementation and modifying the padding function to properly charge the context's memory limit and use efficient string repetition. Until upgrading, no effective mitigation exists because the vulnerability bypasses the engine's memory and render limits.

Description

LiquidJS versions prior to 10.26.0 contain a vulnerability in the `date` filter's strftime implementation that allows unbounded width padding. This flaw bypasses the engine's memory and render limits by passing unchecked large width specifiers to a padding function, causing excessive memory allocation and CPU usage. An attacker can exploit this by supplying a crafted date format string, leading to denial of service via high resource consumption or process crash due to out-of-memory conditions. The vulnerability is fixed in version 10.26.0.

Impact

This vulnerability enables denial of service attacks against any LiquidJS-rendered surface where an attacker can influence the date format string passed to the `date` filter. Exploitation results in excessive memory allocation and CPU usage, potentially causing multi-megabyte outputs, significant processing delays, or out-of-memory crashes that terminate the host process. The attack bypasses the engine's documented memory and render limits, rendering existing DoS protections ineffective for this code path. There is no impact on confidentiality or integrity, only availability.

Summary

The `date` filter in LiquidJS uses a strftime implementation that parses width specifiers (e.g., `%9999999d`) and forwards them unchecked to a padding function (`pad()` in `underscore.ts`). This function performs an unbounded loop concatenating strings without consulting the configured `memoryLimit` or `renderLimit`, allowing attackers to generate multi-megabyte outputs and consume excessive CPU. The documented DoS protections (`memoryLimit` and `renderLimit`) are bypassed because only the input sizes are charged, not the output padding. The vulnerability can be triggered by attacker-controlled input passed as the date format string, a common usage pattern. The issue is distinct from previously reported quadratic replace vulnerabilities and affects all versions before 10.26.0. The fix involves capping the padding width and charging memory usage properly, as implemented in version 10.26.0.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 16:45 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats