EUVD-2026-56782Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Network-reachable API requires guest membership (PR:L); raw OAuth token return is C:H; no direct integrity or availability impact on the vulnerable Typebot system itself.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
4DescriptionCVE.org
TypeBot is a chatbot builder tool. Versions prior to 3.17.0 allow a low-privilege guest member of a workspace to obtain a live Google Sheets OAuth access token for that workspace by calling the Google Sheets helper getAccessToken. The vulnerable path checks only whether the caller has read access to the workspace, decrypts the stored Google OAuth credential, refreshes or retrieves the access token through the Google client, and returns the raw bearer token directly to the caller. Because guest members can also enumerate credential identifiers, a guest can mint and reuse the workspace's Google access token outside Typebot. Version 3.17.0 patches the issue.
AnalysisAI
Typebot's Google Sheets OAuth integration exposes live workspace-level bearer tokens to any guest member via the getAccessToken helper, which checked only for read-level workspace membership before decrypting and returning the raw credential. Versions prior to 3.17.0 allow a low-privileged guest to enumerate credential identifiers, invoke the endpoint, and reuse the workspace's Google OAuth token entirely outside Typebot to access or manipulate connected Google Sheets. No CISA KEV listing exists at time of analysis, but SSVC classifies exploitation status as proof-of-concept with network attack vector and low privilege required, making this a realistic threat for any Typebot workspace with Google Sheets integrations.
Technical ContextAI
Typebot (typebot.io) is an open-source chatbot builder with cloud and self-hosted deployments that integrates with Google Sheets via OAuth. The vulnerable component is the Google Sheets helper route getAccessToken within apps/builder/src/features/blocks/integrations/googleSheets/ of the builder application. The root cause (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) is an authorization logic flaw: the endpoint checked whether the caller held any workspace membership - including read-only guest roles - rather than requiring write-level access before proceeding to decrypt the stored Google OAuth credential, refresh the token via the Google client, and return the raw bearer string. The fix introduced in commit c0ffd825 replaces this with isWriteWorkspaceForbidden and isWriteTypebotForbidden guards, elevating the required permission tier. Affected product per EUVD-2026-56782: typebot.io builder versions prior to 3.17.0.
RemediationAI
Upgrade Typebot to version 3.17.0 or later, which is the vendor-confirmed patched release. The fix is available at the v3.17.0 GitHub release tag and via commit c0ffd825e2f4ee2256a157fd085fb624dcede625; the security advisory is at https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-qjpp-9cqc-jhh8. If immediate upgrade is not possible, three specific compensating controls apply with noted trade-offs: first, remove all guest-role members from workspaces that have Google Sheets OAuth credentials configured - this eliminates the exploitable principal set but may disrupt legitimate read-only collaboration. Second, revoke and delete the Google OAuth credentials stored in affected workspaces via Google's account security settings to invalidate any bearer tokens that may have already been exfiltrated, then re-authorize after patching. Third, disconnect Google Sheets integrations entirely from workspaces with guest members until the upgrade is applied, at the cost of losing that integration's bot functionality.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today