CVE-2026-69222

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
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 in pure JavaScript. Prior to 10.27.2, the join filter in src/filters/array.ts computes complexity from array.length and separator length instead of the total string length produced by array.join(sep). The concat filter can cheaply double arrays of references, after which join materializes the referenced content while charging only for element count, allowing a template to exceed a configured memoryLimit by a large factor. The sibling array_to_sentence_string filter in src/filters/string.ts has the same accounting defect, and a crafted template can allocate toward V8's string or process memory limit and crash the process. This issue is fixed in version 10.27.2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

v10.27.2

Patch available: harttle/liquidjs v10.27.2

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

commit 7ab49f999ac0 (harttle/liquidjs)

Patch available: harttle/liquidjs v11.0.0-alpha.1 (contains commit 7ab49f999ac0)

https://github.com/harttle/liquidjs/commit/7ab49f999ac045ec1e87f3a7a9fd68dd9e8602b3
github_pr Patch Available

fix: charge join/json/inspect filters by produced output size

Patch available: harttle/liquidjs v11.0.0-alpha.1 (PR #925 merged 2026-07-06)

https://github.com/harttle/liquidjs/pull/925
github Patch Available🟡 PoC Available

Uncontrolled Resource Consumption in `join` filter allows template authors to bypass `memoryLimit` and crash the process · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-4r6h-5v86-94p3

Vendor Advisories for CVE-2026-69222(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
liquidjs10.27.2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 52× 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.

  1. 2026-09-18 22:16 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:28 UTCEG score recompute
  4. 2026-09-16 20:05 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 04:10 UTCEG score recompute
  8. 2026-09-14 03:21 UTCEG score recompute
  9. 2026-09-13 02:18 UTCEG score recompute
  10. 2026-09-12 01:30 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 13:06 UTCEG score recompute
  13. 2026-09-11 09:37 UTCEPSS rescore
  14. 2026-09-10 12:18 UTCEG score recompute
  15. 2026-09-09 02:14 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 04:14 UTCEG score recompute
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 14:48 UTCEG score recompute
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-06 02:24 UTCEG score recompute
  22. 2026-09-05 15:31 UTCEPSS rescore
  23. 2026-09-05 01:32 UTCEG score recompute
  24. 2026-09-04 13:08 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 30 more
  1. 2026-09-02 23:51 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 22:56 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 10:33 UTCEG score recompute
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 21:15 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 08:51 UTCEG score recompute
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-29 08:00 UTCEG score recompute
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-27 14:58 UTCEG score recompute
  14. 2026-08-27 02:34 UTCEG score recompute
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 01:39 UTCEG score recompute
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 00:51 UTCEG score recompute
  19. 2026-08-24 12:28 UTCEG score recompute
  20. 2026-08-23 11:38 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 10:50 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 22:26 UTCEG score recompute
  25. 2026-08-21 22:00 UTCEG score recompute
  26. 2026-08-21 10:30 UTCEG score recompute
  27. 2026-08-20 22:56 UTCEPSS rescore
  28. 2026-08-19 21:19 UTCEG score recompute
  29. 2026-08-19 21:04 UTCEG score recompute
  30. 2026-08-19 21:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69222?
CVE-2026-69222 is a high vulnerability published on August 19, 2026. LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.2, the join filter in src/filters/array.ts computes complexity from array.length and separator length instead of the total string length produced by array.join(sep). The concat filter can cheaply…
When was CVE-2026-69222 disclosed?
CVE-2026-69222 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69222 actively exploited?
CVE-2026-69222 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 69.6% of all scored CVEs.
What is the CVSS score of CVE-2026-69222?
CVE-2026-69222 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-69222?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69222, 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-69222

Explore →

Is Your Infrastructure Affected by CVE-2026-69222?

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