Authenticated file read via uncontained template resolution
Published Mar 20, 2026 · Updated Mar 20, 2026
SSTI in Uptime Kuma 1.23.0 through 2.2.0 allows remote authenticated users to read server files through notification templates. The LiquidJS fallback in liquid.node.js passes unquoted absolute template paths to require.resolve without a containment check after configured root restrictions are bypassed. Any authenticated account can submit a render or include tag, exposing any file readable by the Node.js process through an attacker-controlled webhook.
Summary
What happened
SSTI in Uptime Kuma 1.23.0 through 2.2.0 allows remote authenticated users to read server files through notification templates. The LiquidJS fallback in liquid.node.js passes unquoted absolute template paths to require.resolve without a containment check after configured root restrictions are bypassed. Any authenticated account can submit a render or include tag, exposing any file readable by the Node.js process through an attacker-controlled webhook.
The record
- CVE
- CVE-2026-33130
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Louis Lam
- Product
- Uptime Kuma
- Classifications
- CWE-98, CWE-1336, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=>= 1.23.0, < 2.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Authenticated notification-template file-read 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