CVE-2026-33621

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.8 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-16403 (ENISA EUVD) · GHSA-j65m-hv65-r264 (GitHub Security Advisories) · GO-2026-4821 (OSV.dev)Source: ENISA EUVD

6.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: 6.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.7.7 through v0.8.4 contain incomplete request-throttling protections for auth-checkable endpoints. In v0.7.7 through v0.8.3, a fully implemented RateLimitMiddleware existed in internal/handlers/middleware.go but was not inserted into the production HTTP handler chain, so requests were not subject to the intended per-IP throttle. In the same pre-v0.8.4 range, the original limiter also keyed clients using X-Forwarded-For, which would have allowed client-controlled header spoofing if the middleware had been enabled. v0.8.4 addressed those two issues by wiring the limiter into the live handler chain and switching the key to the immediate peer IP, but it still exempted /health and /metrics from rate limiting even though /health remained an auth-checkable endpoint when a token was configured. This issue weakens defense in depth for deployments where an attacker can reach the API, especially if a weak human-chosen token is used. It is not a direct authentication bypass or token disclosure issue by itself. PinchTab is documented as local-first by default and uses 127.0.0.1 plus a generated random token in the recommended setup. PinchTab's default deployment model is a local-first, user-controlled environment between the user and their agents; wider exposure is an intentional operator choice. This lowers practical risk in the default configuration, even though it does not by itself change the intrinsic base characteristics of the bug. This was fully addressed in v0.8.5 by applying RateLimitMiddleware in the production handler chain, deriving the client address from the immediate peer IP instead of trusting forwarded headers by default, and removing the /health and /metrics exemption so auth-checkable endpoints are throttled as well.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.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
24th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.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 3, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Rate Limiting Middleware Defined but Never Applied Allows Unbounded Brute-Force of API Token · Advisory · pinchtab/pinchtab · GitHub

https://github.com/pinchtab/pinchtab/security/advisories/GHSA-j65m-hv65-r264
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 c619c43a4f29 (pinchtab/pinchtab)

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

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/pinchtab/pinchtab @ 0.8.5 (fixes >= 0.7.7, < 0.8.5)—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—
  • 0.7.7 up to 0.8.5: fixed in 0.8.5
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 216 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 119 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% · 24th percentile
  2. 2026-11-01 07:53 UTCGHSA enrichmentGHSA-j65m-hv65-r264 · GitHub severity MODERATE · GitHub CVSS 4.8
  3. 2026-11-01 07:53 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-30 20:55 UTCOSV refresh
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-25 14:34 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-23 03:30 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-18 03:46 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 72 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th 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% · 36th percentile
  8. 2026-10-11 04:31 UTCOSV refresh
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-21 16:19 UTCOSV refresh
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  26. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  29. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-02 13:26 UTCOSV refresh
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  42. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-16 10:05 UTCEG score recompute
  58. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-14 06:23 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-12 23:08 UTCEG score recompute
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-08-12 01:29 UTCEG score recompute
  65. 2026-08-11 03:50 UTCEG score recompute
  66. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-08-10 03:36 UTCEG score recompute
  68. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-08-09 05:56 UTCEG score recompute
  70. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  71. 2026-08-07 16:22 UTCEG score recompute
  72. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33621?
CVE-2026-33621 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.7.7 through v0.8.4 contain incomplete request-throttling protections for auth-checkable endpoints. In v0.7.7 through v0.8.3, a fully implemented RateLimitMiddleware existed in…
When was the CVE record for CVE-2026-33621 published?
The CVE record for CVE-2026-33621 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-33621 actively exploited?
CVE-2026-33621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33621?
CVE-2026-33621 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-33621?
A fix for CVE-2026-33621 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-33621

Explore →

Is Your Infrastructure Affected by CVE-2026-33621?

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

Book a Demo →Browse All CVEs