What is the CVSS score of CVE-2026-42142?

CVE-2026-42142 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N. EPSS exploitation probability: 0.3%.

Which versions of Typebot are affected by CVE-2026-42142?

Typebot versions prior to 3.17.0 expose Google Sheets OAuth credentials to any authenticated user, allowing credential theft across workspace boundaries in multi-tenant deployments.. A patch is available.

How to fix or mitigate CVE-2026-42142?

Within 24 hours: identify all Typebot instances and audit which have active Google Sheets integrations; disable Google Sheets integrations or implement network restrictions on the POST /api/sheets/getSheets endpoint. Within 7 days: upgrade Typebot to version 3.17.0 or later; rotate all Google OAuth tokens previously integrated with Typebot; re-enable Google Sheets integrations only after successful upgrade verification. Within 30 days: audit access logs for unauthorized calls to POST /api/sheets/getSheets endpoint to identify any credential exposure events; review Google account access logs for anomalies during the exposure window; implement endpoint-level access controls and audit logging for all credential-handling APIs.

Typebot CVE-2026-42142

EUVD-2026-56235 HIGH

Missing Authorization (CWE-862)

2026-08-11 GitHub_M

Authentication Bypass Google Typebot Io Baptistearno

7.1

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

vuln.today AI

7.1 HIGH

PR:L confirmed by required authenticated session; C:H from decrypted OAuth credential exposure; I:L from potential downstream Google API write abuse via stolen tokens; A:N as no availability impact applies.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

Patch available

Aug 11, 2026 - 17:02 EUVD

Source Code Evidence Fetched

Aug 11, 2026 - 16:32 vuln.today

Analysis Generated

Aug 11, 2026 - 16:32 vuln.today

CVE Published

Aug 11, 2026 - 15:45 cve.org

HIGH 7.1

DescriptionCVE.org

TypeBot is a chatbot builder tool. Prior to version 3.17.0, the handleGetSheets API handler (POST /api/sheets/getSheets) does not validate workspace membership, allowing any authenticated user to access and decrypt another workspace's Google Sheets OAuth credentials and retrieve spreadsheet data (sheet names, IDs, column headers). Version 3.17.0 fixes the issue.

AnalysisAI

Unauthorized cross-workspace Google Sheets credential exposure in Typebot prior to version 3.17.0 allows any authenticated user to call the POST /api/sheets/getSheets endpoint with an arbitrary workspace ID, bypassing membership checks entirely. The handler decrypts and returns the target workspace's stored Google Sheets OAuth tokens along with spreadsheet metadata (sheet names, IDs, and column headers), constituting a direct credential theft vector against any workspace with a Google Sheets integration configured. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the low exploitation complexity makes this a credible insider or multi-tenant threat.

Technical ContextAI

Typebot (cpe:2.3:a:baptistearno:typebot.io:*:*:*:*:*:*:*:*) is an open-source chatbot builder implemented as a Next.js monorepo. Its Google Sheets integration stores OAuth credentials per workspace in a Prisma-managed database, with credentials encrypted at rest. The handleGetSheets API handler (apps/builder/src/features/blocks/integrations/googleSheets/api/handleGetSheets.ts) accepted a caller-supplied workspaceId parameter and decrypted then returned credentials for that workspace without verifying that the authenticated caller was a member of that workspace. CWE-862 (Missing Authorization) is the precise root cause: the function had authentication (a valid user session) but no authorization check - it never called isReadWorkspaceForbidden or any equivalent membership gate. The PR diff confirms the fix adds a prisma.workspace.findFirst lookup followed by an isReadWorkspaceFobidden(workspace, user) guard that throws ORPCError('NOT_FOUND') on mismatch, preventing unauthorized callers from reaching the credential decryption logic.

RemediationAI

Upgrade to Typebot version 3.17.0, which introduces mandatory workspace membership validation in the handleGetSheets handler before any credential decryption occurs. The fix is confirmed via GitHub release tag v3.17.0 (https://github.com/baptisteArno/typebot.io/releases/tag/v3.17.0) and the merged PR at https://github.com/baptisteArno/typebot.io/pull/2467. For operators unable to upgrade immediately, a targeted compensating control is to revoke and rotate all Google Sheets OAuth credentials stored in affected Typebot workspaces via the Google Account security console - this eliminates the value of any credentials already exfiltrated. Additionally, network-level restriction of the POST /api/sheets/getSheets endpoint to trusted IP ranges (e.g., only builder UI origins via a reverse proxy rule) would raise the bar for exploitation, though it does not close the authorization gap. Disabling Google Sheets integrations workspace-wide until patching is complete is the most conservative option, with the trade-off that all Sheets-dependent chatbot flows will break. Rotating credentials post-patch is strongly recommended to address any pre-patch exfiltration.