CVE-2026-33620

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-33620", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-23T14:24:11.616Z", "datePublished": "2026-03-26T20:40:27.026Z", "dateUpdated": "2026-03-30T14:54:23.611Z"}, "containers": {"cna": {"title": "PinchTab: API Bearer Token Exposed in URL Query Parameter via Server Logs and Intermediary Systems", "problemTypes": [{"descriptions": [{"cweId": "CWE-598", "lang": "en", "description": "CWE-598: Use of GET Request Method With Sensitive Query Strings", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8"}, {"name": "https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4", "tags": ["x_refsource_MISC"], "url": "https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4"}], "affected": [{"vendor": "pinchtab", "product": "pinchtab", "versions": [{"version": ">= 0.7.8, < 0.8.4", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T20:40:27.026Z"}, "descriptions": [{"lang": "en", "value": "PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.7.8` through `v0.8.3` accepted the API token from a `token` URL query parameter in addition to the `Authorization` header. When a valid API credential is sent in the URL, it can be exposed through request URIs recorded by intermediaries or client-side tooling, such as reverse proxy access logs, browser history, shell history, clipboard history, and tracing systems that capture full URLs. This issue is an unsafe credential transport pattern rather than a direct authentication bypass. It only affects deployments where a token is configured and a client actually uses the query-parameter form. PinchTab's security guidance already recommended `Authorization: Bearer <token>`, but `v0.8.3` still accepted `?token=` and included first-party flows that generated and consumed URLs containing the token. This was addressed in v0.8.4 by removing query-string token authentication and requiring safer header- or session-based authentication flows."}], "source": {"advisory": "GHSA-mrqc-3276-74f8", "discovery": "UNKNOWN"}}, "adp": [{"references": [{"url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8", "tags": ["exploit"]}], "metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-03-30T14:43:41.545447Z", "id": "CVE-2026-33620", "options": [{"Exploitation": "poc"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-30T14:54:23.611Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-33620", "role": "CISA Coordinator", "options": [{"Exploitation": "poc"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-30T14:43:41.545447Z"}}}], "references": [{"url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8", "tags": ["exploit"]}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-30T14:43:53.941Z"}}], "cna": {"title": "PinchTab: API Bearer Token Exposed in URL Query Parameter via Server Logs and Intermediary Systems", "source": {"advisory": "GHSA-mrqc-3276-74f8", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}}], "affected": [{"vendor": "pinchtab", "product": "pinchtab", "versions": [{"status": "affected", "version": ">= 0.7.8, < 0.8.4"}]}], "references": [{"url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8", "name": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4", "name": "https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.7.8` through `v0.8.3` accepted the API token from a `token` URL query parameter in addition to the `Authorization` header. When a valid API credential is sent in the URL, it can be exposed through request URIs recorded by intermediaries or client-side tooling, such as reverse proxy access logs, browser history, shell history, clipboard history, and tracing systems that capture full URLs. This issue is an unsafe credential transport pattern rather than a direct authentication bypass. It only affects deployments where a token is configured and a client actually uses the query-parameter form. PinchTab's security guidance already recommended `Authorization: Bearer <token>`, but `v0.8.3` still accepted `?token=` and included first-party flows that generated and consumed URLs containing the token. This was addressed in v0.8.4 by removing query-string token authentication and requiring safer header- or session-based authentication flows."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-598", "description": "CWE-598: Use of GET Request Method With Sensitive Query Strings"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T20:40:27.026Z"}}}, "cveMetadata": {"cveId": "CVE-2026-33620", "state": "PUBLISHED", "dateUpdated": "2026-03-30T14:54:23.611Z", "dateReserved": "2026-03-23T14:24:11.616Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-03-26T20:40:27.026Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "pinchtab", "vendor": "pinchtab", "versions": [{"status": "affected", "version": ">= 0.7.8, < 0.8.4"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:pinchtab:pinchtab:*:*:*:*:*:*:*:*", "matchCriteriaId": "63622A95-2D68-404C-9E53-A6D65A4E8629", "versionEndExcluding": "0.8.4", "versionStartIncluding": "0.7.8", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "PinchTab is a standalone HTTP server that gives AI agents direct control over a Chrome browser. PinchTab `v0.7.8` through `v0.8.3` accepted the API token from a `token` URL query parameter in addition to the `Authorization` header. When a valid API credential is sent in the URL, it can be exposed through request URIs recorded by intermediaries or client-side tooling, such as reverse proxy access logs, browser history, shell history, clipboard history, and tracing systems that capture full URLs. This issue is an unsafe credential transport pattern rather than a direct authentication bypass. It only affects deployments where a token is configured and a client actually uses the query-parameter form. PinchTab's security guidance already recommended `Authorization: Bearer <token>`, but `v0.8.3` still accepted `?token=` and included first-party flows that generated and consumed URLs containing the token. This was addressed in v0.8.4 by removing query-string token authentication and requiring safer header- or session-based authentication flows."}, {"lang": "es", "value": "PinchTab es un servidor HTTP independiente que otorga a los agentes de IA control directo sobre un navegador Chrome. PinchTab 'v0.7.8' hasta 'v0.8.3' aceptaba el token de la API de un par\u00e1metro de consulta URL 'token' adem\u00e1s del encabezado 'Authorization'. Cuando una credencial de API v\u00e1lida se env\u00eda en la URL, puede ser expuesta a trav\u00e9s de URIs de solicitud registradas por intermediarios o herramientas del lado del cliente, como registros de acceso de proxy inverso, historial del navegador, historial de shell, historial del portapapeles y sistemas de rastreo que capturan URLs completas. Este problema es un patr\u00f3n de transporte de credenciales inseguro en lugar de una omisi\u00f3n de autenticaci\u00f3n directa. Solo afecta a las implementaciones donde se configura un token y un cliente realmente utiliza la forma de par\u00e1metro de consulta. La gu\u00eda de seguridad de PinchTab ya recomendaba 'Authorization: Bearer ', pero 'v0.8.3' a\u00fan aceptaba '?token=' e inclu\u00eda flujos de primera parte que generaban y consum\u00edan URLs que conten\u00edan el token. Esto se abord\u00f3 en v0.8.4 al eliminar la autenticaci\u00f3n de token en la cadena de consulta y al requerir flujos de autenticaci\u00f3n m\u00e1s seguros basados en encabezados o en la sesi\u00f3n."}], "id": "CVE-2026-33620", "lastModified": "2026-06-17T10:37:47.880", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 1.4, "source": "security-advisories@github.com", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 1.4, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-33620", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-03-30T14:43:41.545447Z", "version": "2.0.3"}}]}, "published": "2026-03-26T21:17:06.410", "references": [{"source": "security-advisories@github.com", "tags": ["Product", "Release Notes"], "url": "https://github.com/pinchtab/pinchtab/releases/tag/v0.8.4"}, {"source": "security-advisories@github.com", "tags": ["Exploit", "Mitigation", "Vendor Advisory"], "url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8"}, {"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "tags": ["Exploit", "Mitigation", "Vendor Advisory"], "url": "https://github.com/pinchtab/pinchtab/security/advisories/GHSA-mrqc-3276-74f8"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-598"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0.7.8,0.8.4)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "pinchtab", "source": "cna", "vendor": "pinchtab"}, "product": "pinchtab", "vendor": "pinchtab"}], "analysis": {"en": {"generated_at": "2026-03-31T17:35:53.356501+00:00", "value": {"mitigation_remediation": ["Update PinchTab to version 0.8.4 or later to remove query\u2011string token authentication.", "Verify that no older versions are running in the environment.", "Review and purge any logs, browser history, or shell history that may contain URLs with revealed tokens.", "Rotate or revoke any API tokens that may have been exposed.", "Ensure future deployments enforce bearer header or session\u2011based authentication only."], "summary": {"action": "Patch", "impact": "Bearer token exposed in URL and could be logged or leaked"}, "threat_synthesis": {"affected_systems": "The affected product is PinchTab, a standalone HTTP server that gives AI agents control over a Chrome browser. The vulnerability exists in releases from version 0.7.8 up to, but not including, version 0.8.4. Deployments that have token authentication enabled and use the query\u2011parameter form are impacted. PinchTab\u2019s own security guidance recommended using the Authorization bearer header, and the vendor removed query\u2011string token authentication in v0.8.4.", "description_and_impact": "PinchTab versions 0.7.8 through 0.8.3 accepted API tokens via a query parameter named token in addition to the recommended Authorization header. When a token is passed in this way the full request URL, which contains the bearer token, can be written to logs, stored in browser history, captured by shell history, or transmitted to other systems that record entire URLs. This exposes bearer credentials to anyone who can read these logs or history entries, providing a pathway for credential theft. The weakness corresponds to CWE-598, an unsafe credential transport pattern. No direct authentication bypass occurs, but the confidentiality of the token is compromised.", "risk_and_exploitability": "The CVSS score of 4.3 indicates moderate impact with mainly confidentiality concerns. The EPSS score is below 1%, suggesting low probability of mass exploitation at present, and it is not listed in the CISA KEV catalog. Exploitation requires the attacker to either intercept network traffic or to gain read access to the environment where request URLs are logged or stored. Because the token is transmitted over the wire, an adversary could obtain it from logs, browser history, or shell history if they can read those files or processes. The risk is therefore limited to environments where the query\u2011parameter form is in use and logs are accessible to potential attackers. The vendor\u2019s fix in v0.8.4 eliminates the possibility of this credential leakage."}}}}, "created": "2026-03-27T08:32:00.398353+00:00", "updated": "2026-03-31T20:08:40.625769+00:00", "vendors": ["pinchtab", "pinchtab$PRODUCT$pinchtab"]}