PinchTab has Unauthenticated Blind SSRF in Task Scheduler via Unvalidated callbackUrl

Exploitation

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

CVSS

4.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N

EPSS

• CVE-2026-33619: 0.26% estimated exploitation activity in the next 30 days; percentile 17.57 (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 contains a server-side request forgery issue in the optional scheduler's webhook delivery path. When a task is submitted to POST /tasks with a user-controlled callbackUrl, the v0.8.3 scheduler sends an outbound HTTP POST to that URL when the task reaches a terminal state. In that release, the webhook path validated only the URL scheme and did not reject loopback, private, link-local, or other non-public destinations. Because the v0.8.3 implementation also used the default HTTP client behavior, redirects were followed and the destination was not pinned to validated IPs. This allowed blind SSRF from the PinchTab server to attacker-chosen HTTP(S) targets reachable from the server. This issue is narrower than a general unauthenticated internet-facing SSRF. The scheduler is optional and off by default, and in token-protected deployments the attacker must already be able to submit tasks using the server's master API token. In PinchTab's intended deployment model,…

Published by the source

24 Mar 2026, 19:32 UTC

Last modified by the source

27 Apr 2026, 16:18 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xqq2-4j46-vwp7

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

# Patch Next advisory brief: CVE-2026-33619

Advisory: PinchTab has Unauthenticated Blind SSRF in Task Scheduler via Unvalidated callbackUrl
IDs: CVE-2026-33619, GHSA-xqq2-4j46-vwp7
Record: https://patchnext.com/advisories/cve-2026-33619 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pinchtab/pinchtab 0.8.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pinchtab/pinchtab: affected <= 0.8.3; fixed in 0.8.4

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pinchtab/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-xqq2-4j46-vwp7 (GitHub-reviewed advisory GHSA-xqq2-4j46-vwp7 lists affected ranges: Go github.com/pinchtab/pinchtab >=0 <=0.8.3)

Commands are suggestions: review each one before running it.