A PinchTab Security Policy Bypass in /wait Allows Arbitrary JavaScript Execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-33622: 0.53% estimated exploitation activity in the next 30 days; percentile 45.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details Issue 1 — /evaluate enforced the…

Published by the source

24 Mar 2026, 19:43 UTC

Last modified by the source

27 Mar 2026, 21:19 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w5pc-m664-r62v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33622

Advisory: A PinchTab Security Policy Bypass in /wait Allows Arbitrary JavaScript Execution
IDs: CVE-2026-33622, GHSA-w5pc-m664-r62v
Record: https://patchnext.com/advisories/cve-2026-33622 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pinchtab/pinchtab: affected >= 0.8.3
- Go github.com/pinchtab/pinchtab/cmd/pinchtab: affected >= 0.8.3, <= 0.8.5

## Suggested inspection (read-only)
- Go github.com/pinchtab/pinchtab: check the installed version with your package manager.
- Go github.com/pinchtab/pinchtab/cmd/pinchtab: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pinchtab/pinchtab, github.com/pinchtab/pinchtab/cmd/pinchtab.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w5pc-m664-r62v (GitHub-reviewed advisory GHSA-w5pc-m664-r62v lists affected ranges: Go github.com/pinchtab/pinchtab/cmd/pinchtab >=0.8.3 =0.8.3)

Commands are suggestions: review each one before running it.