# CVE-2026-33622: A PinchTab Security Policy Bypass in /wait Allows Arbitrary JavaScript Execution

> Authenticated attackers can execute arbitrary JavaScript in PinchTab via /wait endpoints, bypassing the disabled security policy for code evaluation.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-w5pc-m664-r62v, GO-2026-4824

## What is CVE-2026-33622?

CVE-2026-33622 is a medium-severity code injection vulnerability in pinchtab, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.8.3` through `v0.8.5` allow arbitrary JavaScript execution through `POST /wait` and `POST /tabs/{id}/wait` when the request uses `fn` mode, even if `security.allowEvaluate` is disabled. `POST /evaluate` correctly enforces the `security.allowEvaluate` guard, which is disabled by default. However, in the affected releases, `POST /wait` accepted a user-controlled `fn` expression, embedded it directly into executable JavaScript, and evaluated it in the browser context without checking the same policy. This is a security-policy bypass rather than a separate authentication bypass. Exploitation still requires authenticated API access, but a caller with the server token can execute arbitrary JavaScript in a tab context even when the operator explicitly disabled JavaScript evaluation. The current worktree fixes this by applying the same policy boundary to `fn` mode in `/wait` that already exists on `/evaluate`, while preserving the non-code wait modes. As of time of publication, a patched version is not yet available.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-693 (Protection Mechanism Failure), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-33622?

5 open source packages ship an affected version, including github.com/pinchtab/pinchtab and github.com/pinchtab/pinchtab/cmd/pinchtab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pinchtab/pinchtab` | Go | From 0.8.3 | None |
| `github.com/pinchtab/pinchtab` | Go | From 0.8.3 | None |
| `github.com/pinchtab/pinchtab` | Go | From 0.8.3 | None |
| `github.com/pinchtab/pinchtab/cmd/pinchtab` | Go | From 0.8.3 to 0.8.5 | None |
| `github.com/pinchtab/pinchtab/cmd/pinchtab` | Go | From 0.8.3 to 0.8.5 | None |

Products: Pinchtab Pinchtab.

## How do I fix CVE-2026-33622?

No fix published yet.

## Is CVE-2026-33622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33622 exists.

## Other vulnerabilities in pinchtab

- [CVE-2026-30834](https://insights.sbomify.com/CVE-2026-30834/): PinchTab: SSRF with Full Response Exfiltration via Download Handler (high 7.5)
- [CVE-2026-33623](https://insights.sbomify.com/CVE-2026-33623/): PinchTab: OS Command Injection via Profile Name in Windows Cleanup Routine Enables Arbitrary Command Execution (medium 6.7)
- [CVE-2026-33081](https://insights.sbomify.com/CVE-2026-33081/): PinchTab has Blind SSRF via browser-side redirect bypass in /download URL validation (medium 5.8)
- [CVE-2026-33621](https://insights.sbomify.com/CVE-2026-33621/): PinchTab: Unapplied Rate Limiting Middleware Allows Unbounded Brute-Force of API Token (medium 4.8)
- [CVE-2026-33620](https://insights.sbomify.com/CVE-2026-33620/): PinchTab: API Bearer Token Exposed in URL Query Parameter via Server Logs and Intermediary Systems (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33622 and fix it if it is affected.

What it is: CVE-2026-33622 is a medium-severity code injection vulnerability in pinchtab, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33622 exists.

Affected packages and fixed versions:
- github.com/pinchtab/pinchtab (Go): affected from 0.8.3; no fix listed
- github.com/pinchtab/pinchtab (Go): affected from 0.8.3; no fix listed
- github.com/pinchtab/pinchtab (Go): affected from 0.8.3; no fix listed
- github.com/pinchtab/pinchtab/cmd/pinchtab (Go): affected from 0.8.3 up to 0.8.5; no fix listed
- github.com/pinchtab/pinchtab/cmd/pinchtab (Go): affected from 0.8.3 up to 0.8.5; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33622/ (Markdown: https://insights.sbomify.com/CVE-2026-33622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33622
- OSV: https://osv.dev/vulnerability/CVE-2026-33622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33622/
Summaries are generated and may contain mistakes; the official description above is the record.