# CVE-2026-48767: Google Sheets OAuth access token disclosure to guest members via getAccessToken

> Low-privilege guest members can obtain live Google Sheets OAuth access tokens, allowing unauthorized access to workspace data.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-qjpp-9cqc-jhh8

## What is CVE-2026-48767?

CVE-2026-48767 is a high-severity vulnerability in baptisteArno typebot.io, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-48767?


## How do I fix CVE-2026-48767?

No fix has been published for CVE-2026-48767 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48767 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48767 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48767 and fix it if it is affected.

What it is: CVE-2026-48767 is a high-severity vulnerability in baptisteArno typebot.io, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48767 exists.

Affected product: baptisteArno typebot.io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48767/ (Markdown: https://insights.sbomify.com/CVE-2026-48767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48767
- OSV: https://osv.dev/vulnerability/CVE-2026-48767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48767/
Summaries are generated and may contain mistakes; the official description above is the record.