Quick answers
- Is CVE-2026-48495 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48495 being exploited in the wild.
- How severe is CVE-2026-48495?
- High severity, with a CVSS score of 7.1, published 11 August 2026.
- Which products and versions are affected?
- Typebot prior to 3.17.0.
- Is there a fix for CVE-2026-48495?
- A patch was published on 2026-05-21: Fix merged in version 3.17.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48495 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-48495?
- Check whether you run Typebot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a privilege escalation and authorization bypass in the Google Sheets OAuth callback handler. The endpoint decodes a base64-encoded JSON `state` parameter containing `workspaceId`, `typebotId`, `blockId`, and `redirectUrl` without cryptographic signature verification or integrity protection. Although the callback route is authenticated, it fails to validate that the authenticated user has write access to the target workspace or Typebot before creating credentials or updating blocks. An authenticated attacker who obtains a valid Google OAuth `code` can craft a malicious `state` parameter to create Google Sheets credentials in arbitrary workspaces and, with known target IDs, attach those credentials to blocks in other Typebots. Version 3.17.0 resolves this by implementing signed OAuth state payloads with expiry, user binding, HttpOnly nonce cookies, and enforced authorization checks before credential creation and callback side effects.
Affected products
- TypeBot TypeBot prior to 3.17.0
Timeline
- 2026-08-11: disclosed
- 2026-05-21: patched: Fix merged in version 3.17.0