CVE-2026-33619

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-24) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-16400 (ENISA EUVD) · GHSA-xqq2-4j46-vwp7 (GitHub Security Advisories) · GO-2026-4825 (OSV.dev)Source: ENISA EUVD

5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. 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, that token represents administrative control rather than a low-privilege role. Tokenless deployments lower the barrier further, but that is a separate insecure configuration state rather than impact created by the webhook bug itself. PinchTab's default deployment model is local-first and user-controlled, with loopback bind and token-based access in the recommended setup. That lowers practical risk in default use, even though it does not remove the underlying webhook issue when the scheduler is enabled and reachable. This was addressed in v0.8.4 by validating callback targets before dispatch, rejecting non-public IP ranges, pinning delivery to validated IPs, disabling redirect following, and validating callbackUrl during task submission.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated Blind SSRF in Task Scheduler via Unvalidated callbackUrl · Advisory · pinchtab/pinchtab · GitHub

https://github.com/pinchtab/pinchtab/security/advisories/GHSA-xqq2-4j46-vwp7
GitHub release Patch Available

v0.8.4

Patch available: pinchtab/pinchtab v0.8.4

https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4
GitHub commit

commit c824574c3a05 (pinchtab/pinchtab)

Fix landed in pinchtab/pinchtab commit c824574c3a05 — awaiting tagged release

https://github.com/pinchtab/pinchtab/commit/c824574c3a05073dec2f5e9c219e22ffff8de445

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/pinchtab/pinchtab @ 0.8.4 (fixes <= 0.8.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/pinchtab/pinchtab—
  • every version up to 0.8.4: fixed in 0.8.4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 214 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 07:53 UTCGHSA enrichmentGHSA-xqq2-4j46-vwp7 · GitHub severity MODERATE · GitHub CVSS 4.1
  3. 2026-11-01 07:53 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-30 20:55 UTCOSV refresh
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-25 14:34 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-23 03:30 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-18 03:46 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 72 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-12 16:13 UTCEG score recompute
  4. 2026-10-11 19:55 UTCEG score recompute
  5. 2026-10-11 17:08 UTCEG score recompute
  6. 2026-10-11 14:36 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-11 04:31 UTCOSV refresh
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-09-21 16:49 UTCOSV refresh
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  26. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  29. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  31. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  33. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  35. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  38. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  39. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  40. 2026-09-02 13:26 UTCOSV refresh
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  42. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  45. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  46. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  49. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  50. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  54. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  55. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-08-16 10:05 UTCEG score recompute
  58. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  60. 2026-08-14 06:23 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  62. 2026-08-12 20:40 UTCEG score recompute
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  64. 2026-08-11 06:58 UTCEG score recompute
  65. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  66. 2026-08-10 06:27 UTCEG score recompute
  67. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  68. 2026-08-09 05:56 UTCEG score recompute
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  70. 2026-08-07 16:22 UTCEG score recompute
  71. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  72. 2026-08-06 00:50 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33619?
CVE-2026-33619 is a medium-severity vulnerability; its CVE record was published on March 26, 2026. PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. 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…
When was the CVE record for CVE-2026-33619 published?
The CVE record for CVE-2026-33619 was published on March 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-33619 actively exploited?
CVE-2026-33619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33619?
CVE-2026-33619 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-33619?
A fix for CVE-2026-33619 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33619

Explore →

Is Your Infrastructure Affected by CVE-2026-33619?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs