CVE-2026-33620
Last modified
CVE-2026-33620 is a medium-severity vulnerability rated 4.3/10 on the CVSS scale. PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.7.8` through `v0.8.3` accepted the API token from a `token` URL query parameter in addition to the `Authorization` header. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
Description
PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.7.8` through `v0.8.3` accepted the API token from a `token` URL query parameter in addition to the `Authorization` header. When a valid API credential is sent in the URL, it can be exposed through request URIs recorded by intermediaries or client-side tooling, such as reverse proxy access logs, browser history, shell history, clipboard history, and tracing systems that capture full URLs. This issue is an unsafe credential transport pattern rather than a direct authentication bypass. It only affects deployments where a token is configured and a client actually uses the query-parameter form. PinchTab's security guidance already recommended `Authorization: Bearer <token>`, but `v0.8.3` still accepted `?token=` and included first-party flows that generated and consumed URLs containing the token. This was addressed in v0.8.4 by removing query-string token authentication and requiring safer header- or session-based authentication flows.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pinchtab | Pinchtab | >= 0.7.8, < 0.8.4 |
References
- https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4Product, Release Notes
- https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8Exploit, Mitigation, Vendor Advisory
- https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8Exploit, Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-33620?
How severe is CVE-2026-33620?
How do I fix CVE-2026-33620?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-33615An unauthenticated remote attacker can exploit an unauthenti…9.1
- CVE-2026-33616An unauthenticated remote attacker can exploit an unauthenti…7.5
- CVE-2026-33617An unauthenticated remote attacker can access a configuratio…5.3
- CVE-2026-33618Chamilo LMS is a learning management system. Prior to .0.0-R…8.8
- CVE-2026-33619PinchTab is a standalone HTTP server that gives AI agents di…5.5
- CVE-2026-3362The Short Comment Filter plugin for WordPress is vulnerable …4.4
- CVE-2026-33621PinchTab is a standalone HTTP server that gives AI agents di…6.5
- CVE-2026-33622PinchTab is a standalone HTTP server that gives AI agents di…8.8
- CVE-2026-33623PinchTab is a standalone HTTP server that gives AI agents di…7.2
- CVE-2026-33624Parse Server is an open source backend that can be deployed …2.7
- CVE-2026-33626LMDeploy is a toolkit for compressing, deploying, and servin…7.5
- CVE-2026-33627Parse Server is an open source backend that can be deployed …6.5
Are you affected by CVE-2026-33620?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
