CVE-2026-39412 | harttle liquidjs up to 10.25.3 sort_natural information disclosure (GHSA-rv5g-f82m-qrvv)

VDB-356473 · CVE-2026-39412 · GHSA-RV5G-F82M-QRVV HARTTLE LIQUIDJS UP TO 10.25.3 SORT_NATURAL INFORMATION DISCLOSURE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.2 $0-$5k 0.53+ Summaryinfo A vulnerability was found in harttle liquidjs up to 10.25.3. It has been classified as problematic. The impacted element is the function sort_natural. This manipulation causes information disclosure. This vulnerability appears as CVE-2026-39412. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended. Detailsinfo A vulnerability classified as problematic was found in harttle liquidjs up to 10.25.3. Affected by this vulnerability is the function sort_natural. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is: 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. This vulnerability is fixed in 10.25.4. The advisory is shared at github.com. This vulnerability is known as CVE-2026-39412 since 04/07/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue. Upgrading to version 10.25.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e743da0020d34e2ee547e1cc1a86b58377ebe1ce is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor harttle Name liquidjs Version 10.25.0 10.25.1 10.25.2 10.25.3 License open-source Website Product: https://github.com/harttle/liquidjs/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.2 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.3 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Information disclosure CWE: CWE-200 / CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: liquidjs 10.25.4 Patch: e743da0020d34e2ee547e1cc1a86b58377ebe1ce Timelineinfo 04/07/2026 CVE reserved 04/09/2026 +2 days Advisory disclosed 04/09/2026 +0 days VulDB entry created 04/09/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-rv5g-f82m-qrvv Status: Confirmed CVE: CVE-2026-39412 (🔒) GCVE (CVE): GCVE-0-2026-39412 GCVE (VulDB): GCVE-100-356473 Entryinfo Created: 04/09/2026 02:44 Changes: 04/09/2026 02:44 (68) Complete: 🔍 Cache ID: 99:103:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸