API token disclosure via query-string authentication
Published Mar 26, 2026 · Updated Mar 26, 2026
Credential exposure in PinchTab 0.7.8 through 0.8.3 allows attackers to obtain API tokens from recorded query-string request URLs. The authentication middleware reads the token parameter from r.URL.Query and treats it as the bearer credential, while first-party setup and dashboard flows generate and consume tokenized URLs. Exposure requires a configured token, use of the query form, and access to a proxy log, browser or shell history, clipboard history, or tracing record; header-only clients are unaffected.
Summary
What happened
Credential exposure in PinchTab 0.7.8 through 0.8.3 allows attackers to obtain API tokens from recorded query-string request URLs. The authentication middleware reads the token parameter from r.URL.Query and treats it as the bearer credential, while first-party setup and dashboard flows generate and consume tokenized URLs. Exposure requires a configured token, use of the query form, and access to a proxy log, browser or shell history, clipboard history, or tracing record; header-only clients are unaffected.
The record
- CVE
- CVE-2026-33620
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- PinchTab
- Product
- PinchTab
- Classifications
- CWE-598, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 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.8, < 0.8.4
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
- Vendor query-token authentication 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