CVE-2026-106120 harttle CVE debrief

Who should care

Defenders who use LiquidJS in applications with untrusted or prototype-polluted scope data should assess their exposure and prioritize verification and remediation. Defenders should care about CVE-2026-106120 because it affects LiquidJS's `ownPropertyOnly` option, potentially leading to information disclosure when rendering templates over untrusted or prototype-polluted scope data.

Why it matters

Defenders should care about CVE-2026-106120 because it affects LiquidJS's `ownPropertyOnly` option, potentially leading to information disclosure when rendering templates over untrusted or prototype-polluted scope data. The issue requires verification of `ownPropertyOnly: true` usage and scope data trustworthiness, and remediation for affected versions.

• Potential information disclosure through template rendering
• Possible exploitation by attackers who can influence prototype state or inherited array-index data
• Verification priority for `ownPropertyOnly: true` usage and scope data trustworthiness
• Remediation priority for affected versions

Technical summary

LiquidJS's `ownPropertyOnly` option is intended to prevent templates from reading inherited or prototype properties from scope data. However, the option does not consistently block inherited array index reads, potentially leading to information disclosure. The issue requires verification of `ownPropertyOnly: true` usage and scope data trustworthiness, and remediation for affected versions. This information disclosure issue in LiquidJS's `ownPropertyOnly` option allows inherited array index reads to be disclosed through certain methods, despite the option being set to `true`.

Defensive priority

Defenders should prioritize verifying the use of `ownPropertyOnly: true` in LiquidJS templates, especially when rendering over untrusted or prototype-polluted scope data.

Recommended defensive actions

• Verify the use of `ownPropertyOnly: true` in LiquidJS templates
• Assess the impact of prototype pollution on scope data
• Update to version 10.27.2 or later if affected
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the information disclosure issue in LiquidJS's `ownPropertyOnly` option. The issue allows inherited array index reads to be disclosed through certain methods, despite the option being set to `true`.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.