Unauthenticated data exfiltration via unvalidated download URL
Published Mar 7, 2026 · Updated Mar 7, 2026
SSRF in PinchTab before 0.7.7 allows remote attackers to read local files and internal HTTP responses through the /download endpoint. The GET handler in internal/handlers/download.go passes its user-controlled url parameter directly to chromedp.Navigate without validation, then returns the captured response body. The API must be reachable; no configured credential is required, and disclosure is limited to resources accessible from the server's Chrome process.
Summary
What happened
SSRF in PinchTab before 0.7.7 allows remote attackers to read local files and internal HTTP responses through the /download endpoint. The GET handler in internal/handlers/download.go passes its user-controlled url parameter directly to chromedp.Navigate without validation, then returns the captured response body. The API must be reachable; no configured credential is required, and disclosure is limited to resources accessible from the server's Chrome process.
The record
- CVE
- CVE-2026-30834
- Published
- Mar 7, 2026
- Updated
- Mar 7, 2026
- Vendor
- PinchTab
- Product
- PinchTab
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2026CVE publishedPublication date reported by the CVE source.
- Mar 7, 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=< 0.7.7
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
- GitHub maintainer advisory reproduction stepsproof 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