How to Fix CVE-2026-39412: liquidjs (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-39412 is a sibling vulnerability in the same Harttle liquidjs advisory bundle as CVE-2026-34166. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-39412 matches the primary write-up.

What is different about CVE-2026-39412?

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.4, the sort_natural filter bypasses the ownPropertyOnly security option, allowing template authors to extract values of prototype-inherited properties through a sorting side-channel attack. Applications relying on ownPropertyOnly: true as a security boundary (e.g., multi-tenant template systems) are exposed to information disclosure of sensitive prototype properties such as API keys and tokens.

Impact is consistent with the bundle: disclosure of sensitive information. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-39412

Apply the patched build per the primary write-up: How to Fix CVE-2026-34166.

For a quick check, confirm the running version of liquidjs:

# Confirm the installed version via your package manager
dpkg -l | grep -i liquidjs   # Debian/Ubuntu
rpm -qa | grep -i liquidjs   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-39412 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-39412?

CVSS rates it 5.3 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take liquidjs offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-39412 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/harttle/liquidjs/security/advisories/GHSA-rv5g-f82m-qrvv
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-39412
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-34166

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Harttle liquidjs advisory bundle. Full procedure at how-to-fix-cve-2026-34166.*