File disclosure via symlinked template loading
Published Apr 8, 2026 · Updated Apr 8, 2026
CWE-61 in LiquidJS before 10.25.3 allows attackers to read files outside template roots through symlinked partials or layouts. The include, render, and layout loaders validate the requested pathname without resolving its canonical target before opening it. Exploitation requires control of a symlink beneath a trusted template root and exposes any file readable by the LiquidJS process.
Summary
What happened
CWE-61 in LiquidJS before 10.25.3 allows attackers to read files outside template roots through symlinked partials or layouts. The include, render, and layout loaders validate the requested pathname without resolving its canonical target before opening it. Exploitation requires control of a symlink beneath a trusted template root and exposes any file readable by the LiquidJS process.
The record
- CVE
- CVE-2026-35525
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- LiquidJS
- Product
- LiquidJS
- Classifications
- CWE-61, CAPEC-27, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 10.25.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-56p5-8mhr-2fph proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo