Chrome SSRF (CVE-2026-30834)
CVE-2026-30834
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 all...
Overview
A significant security vulnerability has been identified in the PinchTab HTTP server, a tool that allows AI agents to control a Chrome browser. This flaw, tracked as CVE-2026-30834, could allow an attacker to misuse the server to access sensitive internal systems and data. Users are urged to update their software immediately.
Vulnerability Details
In simple terms, this is a Server-Side Request Forgery (SSRF) vulnerability. PinchTab versions before 0.7.7 contain a specific feature, the /download endpoint, that is not properly secured. An attacker with access to the PinchTab API can manipulate this feature. Instead of only downloading intended files, they can force the PinchTab server itself to send requests to any URL the attacker specifies.
This means the attacker can point the server at:
- Other internal services on your network (like databases, admin panels, or file servers).
- Local system files on the machine running PinchTab. The server will then retrieve the full content from these locations and send it back to the attacker, leading to data exfiltration.
Potential Impact
The impact of this vulnerability is high. Successful exploitation could lead to:
- Data Breach: Sensitive information from internal applications and files can be stolen.
- Network Mapping: Attackers can probe your internal network to discover other vulnerable systems.
- Further Attacks: Accessed data or systems could be used as a foothold for more severe attacks, such as ransomware deployment.
For more on the consequences of data exposure, recent incident analyses are available in our breach reports.
Remediation and Mitigation
The primary and most critical action is to upgrade PinchTab to version 0.7.7 or later. This update contains the patch that fixes the SSRF flaw in the /download endpoint.
Immediate Actions:
- Update: Identify all instances of PinchTab in your environment and upgrade them to version 0.7.7+ without delay.
- Access Control: Review and restrict access to the PinchTab API. Ensure only authorized, trusted systems and users can communicate with it, following the principle of least privilege.
- Network Segmentation: As a general security best practice, consider running tools like PinchTab in a segmented network zone to limit their ability to reach critical internal assets, even if a vulnerability is exploited.
Stay informed about emerging threats and patches by following our security news. Prompt patching remains the most effective defense against known vulnerabilities.
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Am I Affected by CVE-2026-30834?
Pick an ecosystem, paste your installed version, and we'll compare it against the fixed version published on OSV.dev. Browser-only — nothing is sent to a server.
Heuristic comparison only. Always cross-check against the vendor advisory before making patching decisions.
Related Advisories
Object lifecycle issue in DevTools in Google Chrome prior to 145.0.7632.159 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a craft...
FastGPT is an AI Agent building platform. Prior to version 4.14.9.5, FastGPT's MCP (Model Context Protocol) tools endpoints (/api/core/app/mcpTools/getTools and /api/core/app/mcpTools/runTool) accept ...
OpenClaw before 2026.3.28 contains a server-side request forgery vulnerability in the fal provider image-generation-provider.ts component that allows attackers to fetch internal URLs. A malicious or c...
A vulnerability was identified in elecV2 elecV2P up to 3.8.3. This affects the function eAxios of the file /mock of the component URL Handler. Such manipulation of the argument req leads to server-sid...