CVE-2026-45357

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the date filter's strftime implementation parses width specifiers like %9999999d and forwards the captured width unchecked into pad()/padStart(), leading to memory and render limit bypass. In src/util/underscore.ts, the pad loop performs unbounded string concatenation without consulting the Context's memoryLimit or renderLimit, so a single small template ({{ x | date: '%5000000d' }}) produces megabytes of output and unbounded CPU. The memoryLimit and renderLimit options the docs (src/liquid-options.ts:87-92) advertise as DoS controls — and which the docstring explicitly mentions for strftime — are entirely bypassed. Exploitation can cause large memory allocations, high CPU usage, or OOM crashes per render. This issue has been fixed in version 10.26.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 22, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Memory and render limit bypass via unbounded width padding in `date` filter (strftime) · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-hh27-hf48-9f5q
github_release Patch Available

v10.26.0

Patch available: harttle/liquidjs v10.26.0

https://github.com/harttle/liquidjs/releases/tag/v10.26.0
github_commit Patch Available

commit 3129d46dc95e (harttle/liquidjs)

Patch available: harttle/liquidjs v10.26.0 (contains commit 3129d46dc95e)

https://github.com/harttle/liquidjs/commit/3129d46dc95efa357b00e5a57ee1af80a13d72ed

Vendor Advisories for CVE-2026-45357(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmliquidjs—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
liquidjs———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 201 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 07:37 UTCEG score recompute
  3. 2026-09-14 07:37 UTCGHSA enrichment
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 03:09 UTCOSV refresh
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 05:12 UTCEG score recompute
  23. 2026-08-25 05:12 UTCGHSA enrichment
  24. 2026-08-23 14:57 UTCEG score recompute
  25. 2026-08-23 14:57 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 20:32 UTCGHSA enrichment
  4. 2026-08-21 01:28 UTCEG score recompute
  5. 2026-08-21 01:28 UTCGHSA enrichment
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 11:15 UTCEG score recompute
  8. 2026-08-20 11:15 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 09:14 UTCGHSA enrichment
  13. 2026-08-16 15:13 UTCEG score recompute
  14. 2026-08-16 15:13 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:47 UTCEG score recompute
  17. 2026-08-16 02:47 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:54 UTCEG score recompute
  20. 2026-08-15 01:54 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 13:40 UTCGHSA enrichment
  23. 2026-08-14 01:25 UTCEG score recompute
  24. 2026-08-14 01:25 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-13 02:21 UTCGHSA enrichment
  27. 2026-08-12 14:07 UTCEG score recompute
  28. 2026-08-12 14:07 UTCGHSA enrichment
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 01:49 UTCEG score recompute
  31. 2026-08-12 01:49 UTCGHSA enrichment
  32. 2026-08-11 13:34 UTCGHSA enrichment
  33. 2026-08-11 00:11 UTCEG score recompute
  34. 2026-08-11 00:11 UTCGHSA enrichment
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 11:14 UTCGHSA enrichment
  37. 2026-08-09 22:58 UTCEG score recompute
  38. 2026-08-09 22:58 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 10:44 UTCGHSA enrichment
  41. 2026-08-08 22:25 UTCEG score recompute
  42. 2026-08-08 22:25 UTCGHSA enrichment
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-08 10:10 UTCGHSA enrichment
  45. 2026-08-07 21:55 UTCEG score recompute
  46. 2026-08-07 21:55 UTCGHSA enrichment
  47. 2026-08-07 09:40 UTCGHSA enrichment
  48. 2026-08-06 21:21 UTCEG score recompute
  49. 2026-08-06 21:21 UTCGHSA enrichment
  50. 2026-08-06 13:47 UTCEPSS rescore
  51. 2026-08-06 09:06 UTCGHSA enrichment
  52. 2026-08-05 20:51 UTCEG score recompute
  53. 2026-08-05 20:51 UTCGHSA enrichment
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-04 04:40 UTCGHSA enrichment
  58. 2026-08-03 16:25 UTCEG score recompute
  59. 2026-08-03 16:25 UTCGHSA enrichment
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 03:55 UTCGHSA enrichment
  62. 2026-08-02 15:40 UTCGHSA enrichment
  63. 2026-08-02 03:25 UTCEG score recompute
  64. 2026-08-02 03:25 UTCGHSA enrichment
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 15:09 UTCEG score recompute
  67. 2026-08-01 15:09 UTCGHSA enrichment
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-31 07:28 UTCEG score recompute
  70. 2026-07-31 07:28 UTCGHSA enrichment
  71. 2026-07-30 16:28 UTCEPSS rescore
  72. 2026-07-30 01:30 UTCEPSS rescore
  73. 2026-07-29 15:01 UTCEG score recompute
  74. 2026-07-29 15:01 UTCGHSA enrichment
  75. 2026-07-28 15:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45357?
CVE-2026-45357 is a high vulnerability published on May 27, 2026. LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the date filter's strftime implementation parses width specifiers like %9999999d and forwards the captured width unchecked into pad()/padStart(), leading to memory and render…
When was CVE-2026-45357 disclosed?
CVE-2026-45357 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45357 actively exploited?
CVE-2026-45357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.9% of all scored CVEs.
What is the CVSS score of CVE-2026-45357?
CVE-2026-45357 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45357, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45357

Explore →

Is Your Infrastructure Affected by CVE-2026-45357?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs