Security readout for executives and security teams
Plain-English summary
A read-only Typebot collaborator can potentially take control of OAuth credentials belonging to another workspace. The vulnerable update process trusts a supplied workspace identifier but changes credentials using a globally valid credential identifier, allowing unauthorized reassignment and replacement. This could expose connected services, corrupt integrations, and cross tenant boundaries.
Executive priority
Treat this as an immediate upgrade and investigation priority, especially in multi-workspace environments with external collaborators. The flaw crosses workspace boundaries and can compromise third-party OAuth integrations. Prioritize credential review and rotation where suspicious changes appear; current sources do not confirm active exploitation.
Technical view
Typebot versions before 3.17.0 contain a CWE-639 authorization flaw in handleUpdateOAuthCredentials(). An attacker with read access can obtain a credentialsId from a readable bot, pass a writable workspaceId, and update the credential by global ID. The operation also rewrites workspaceId, enabling cross-workspace credential takeover without user interaction.
Likely exposure
Exposure exists on Typebot versions earlier than 3.17.0 when a low-privilege read collaborator can access a bot configuration containing an OAuth credentialsId and controls another writable workspace. The supplied sources do not quantify affected deployments or confirm whether additional configuration is required.
Exploitation context
The CVSS 3.1 score is 9.9, reflecting remote, low-complexity exploitation with low privileges and no user interaction. The provided record is not marked as CISA KEV, and the sources supplied do not establish active exploitation in the wild or public weaponization.
Researcher notes
The core defect is missing object-to-workspace binding: authorization checks the caller-controlled workspaceId, while the mutation targets credentials by global id and changes their ownership field. Review logs for both credential content changes and workspaceId transitions. Evidence supplied establishes the vulnerable logic and patch version, but not exploitation prevalence.
Mitigation direction
- Upgrade Typebot to version 3.17.0 or later.
- Restrict collaborator access until all vulnerable instances are upgraded.
- Review affected OAuth credentials and rotate or revoke any suspected of unauthorized modification.
- Check the vendor advisory and release notes for additional remediation guidance.
Validation and detection
- Confirm every Typebot deployment reports version 3.17.0 or later.
- Review audit records for unexpected OAuth credential updates or workspace reassignment.
- Identify read collaborators who could access bots containing OAuth credential references.
- Verify OAuth integrations still belong to their intended workspaces after upgrading.
- Test authorization boundaries using approved defensive tests without accessing another tenant's credentials.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-48765 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-3788-7276-x4j4CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/baptisteArno/typebot.io/pull/2459CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/baptisteArno/typebot.io/commit/7ae4c007d0987d2ca907b47e1b7418db62b8a157CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/baptisteArno/typebot.io/releases/tag/v3.17.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.