CVE-2026-44646

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-27. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 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, Context.spawn() creates a child Context for the {% render %} tag but does not propagate the parent context's resolved ownPropertyOnly value, resulting in a silent bypass. The new context re-derives ownPropertyOnly from opts.ownPropertyOnly (the instance-level option), silently discarding any RenderOptions.ownPropertyOnly override that was supplied to parseAndRender(). As a result, a developer who runs a Liquid instance with the backwards-compatible ownPropertyOnly:false and then locks down an untrusted render with parseAndRender(..., { ownPropertyOnly: true }) still leaks prototype-chain properties from inside any {% render %} partial. This is a distinct exploit surface from the previously identified array-filter variants (where, reject, group_by, find, find_index, has) — the underlying root cause in Context.spawn() is shared, but {% render %} is a separately reachable sink that needs no filter usage. This issue has been fixed in version 10.26.0.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
19.1%
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

liquidjs `{% render %}` tag silently bypasses per-render `ownPropertyOnly:true` via `Context.spawn()` · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-9x9p-qf8f-mvjg
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 dbbf62880305 (harttle/liquidjs)

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

https://github.com/harttle/liquidjs/commit/dbbf6288030591bf6da28d8c1cce5a17bca97bb6

Vendor Advisories for CVE-2026-44646(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 8× in last 7d / 38× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 05:52 UTCOSV refresh
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-07-01 11:53 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-29 20:56 UTCGHSA enrichment
Show 45 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 22:25 UTCGHSA enrichment
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 18:47 UTCGHSA enrichment
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 17:27 UTCGHSA enrichment
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 09:35 UTCGHSA enrichment
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-17 23:37 UTCGHSA enrichment
  23. 2026-06-17 00:47 UTCGHSA enrichment
  24. 2026-06-16 02:16 UTCGHSA enrichment
  25. 2026-06-15 03:46 UTCGHSA enrichment
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-14 05:15 UTCGHSA enrichment
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 06:31 UTCGHSA enrichment
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 07:57 UTCGHSA enrichment
  32. 2026-06-11 09:27 UTCGHSA enrichment
  33. 2026-06-10 10:57 UTCGHSA enrichment
  34. 2026-06-09 12:27 UTCGHSA enrichment
  35. 2026-06-08 13:56 UTCGHSA enrichment
  36. 2026-06-07 15:26 UTCGHSA enrichment
  37. 2026-06-06 16:56 UTCGHSA enrichment
  38. 2026-06-05 18:26 UTCGHSA enrichment
  39. 2026-06-04 19:56 UTCGHSA enrichment
  40. 2026-06-03 21:26 UTCGHSA enrichment
  41. 2026-06-02 22:56 UTCGHSA enrichment
  42. 2026-06-02 00:26 UTCGHSA enrichment
  43. 2026-06-01 01:56 UTCGHSA enrichment
  44. 2026-05-27 01:14 UTCEG score recompute
  45. 2026-05-27 01:14 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-44646?
CVE-2026-44646 is a medium 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, Context.spawn() creates a child Context for the {% render %} tag but does not propagate the parent context's resolved ownPropertyOnly value, resulting in a silent bypass. The new…
When was CVE-2026-44646 disclosed?
CVE-2026-44646 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-44646 actively exploited?
CVE-2026-44646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44646?
CVE-2026-44646 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44646, 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-44646

Explore →

Is Your Infrastructure Affected by CVE-2026-44646?

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

Start Free Scan →Browse All CVEs