File disclosure and SSRF via unchecked stylesheet URI
Published Jun 10, 2026 · Updated Jun 10, 2026
SSRF in KNP Labs Snappy before 1.7.0 allows remote attackers to read local files or fetch internal URLs through xsl-style-sheet. The option handler passes an attacker-controlled stylesheet URI to wkhtmltopdf without restricting its scheme, so file URIs and arbitrary HTTP or HTTPS targets are dereferenced. Exploitation requires a consuming application to expose the option to untrusted input; disclosure depends on the PHP process's access to sensitive files or internal services.
Summary
What happened
SSRF in KNP Labs Snappy before 1.7.0 allows remote attackers to read local files or fetch internal URLs through xsl-style-sheet. The option handler passes an attacker-controlled stylesheet URI to wkhtmltopdf without restricting its scheme, so file URIs and arbitrary HTTP or HTTPS targets are dereferenced. Exploitation requires a consuming application to expose the option to untrusted input; disclosure depends on the PHP process's access to sensitive files or internal services.
The record
- CVE
- CVE-2026-46683
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- KNP Labs
- Product
- Snappy
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 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.7.0
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
- Upstream file URI 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