# CVE-2026-30834: PinchTab: SSRF with Full Response Exfiltration via Download Handler

> Attackers with API access can exploit SSRF in the download handler to access internal services and exfiltrate sensitive data from the PinchTab server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-rw8p-c6hf-q3pg, GO-2026-4631

## What is CVE-2026-30834?

CVE-2026-30834 is a high-severity server-side request forgery vulnerability in pinchtab, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. Prior to version 0.7.7, a Server-Side Request Forgery (SSRF) vulnerability in the /download endpoint allows any user with API access to induce the PinchTab server to make requests to arbitrary URLs, including internal network services and local system files, and exfiltrate the full response content. This issue has been patched in version 0.7.7.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pinchtab/pinchtab/cmd/pinchtab` | Go | All versions | 0.7.7 |
| `github.com/pinchtab/pinchtab/cmd/pinchtab` | Go | All versions | 0.7.7 |
| `github.com/pinchtab/pinchtab` | Go | All versions | 0.7.7 |

Products: Pinchtab Pinchtab.

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

Upgrade github.com/pinchtab/pinchtab/cmd/pinchtab to 0.7.7 or later.

## Is CVE-2026-30834 being exploited?

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

## Other vulnerabilities in pinchtab

- [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-33622](https://insights.sbomify.com/CVE-2026-33622/): A PinchTab Security Policy Bypass in /wait Allows Arbitrary JavaScript Execution (medium 6.1)
- [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-30834 and fix it if it is affected.

What it is: CVE-2026-30834 is a high-severity server-side request forgery vulnerability in pinchtab, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30834 exists.

Affected packages and fixed versions:
- github.com/pinchtab/pinchtab/cmd/pinchtab (Go): affected all versions; fixed in 0.7.7
- github.com/pinchtab/pinchtab/cmd/pinchtab (Go): affected all versions; fixed in 0.7.7
- github.com/pinchtab/pinchtab (Go): affected all versions; fixed in 0.7.7

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-30834/ (Markdown: https://insights.sbomify.com/CVE-2026-30834/index.md)
```

## Sources

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

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