CVE-2026-48766 baptisteArno CVE debrief

Who should care

Defenders responsible for TypeBot workspaces, especially those with guest members, should assess exposure and prioritize updating to version 3.17.0 or later. They should verify TypeBot workspace configurations to prevent unauthorized access, monitor workspaces for suspicious activity related to OpenAI-compatible API keys, and review compensating controls for exposed systems.

Why it matters

CVE-2026-48766 allows low-privilege guest members of a TypeBot workspace to exfiltrate stored OpenAI-compatible API keys. Defenders should verify exposure, prioritize updates, and monitor workspaces.

• Verify TypeBot workspace configurations to prevent unauthorized access.
• Update TypeBot to version 3.17.0 or later to patch the vulnerability.
• Monitor TypeBot workspaces for suspicious activity related to OpenAI-compatible API keys.

Technical summary

The vulnerability in TypeBot allows a low-privilege guest member of a workspace to exfiltrate stored OpenAI-compatible API keys by invoking the OpenAI model-listing helper with an attacker-controlled baseUrl. The vulnerable path decrypts the selected workspace credential, creates an OpenAI client with the secret in both apiKey and the explicit api-key header, and then sends the outbound request to the caller-supplied URL. Because the permission check accepts any readable workspace member and listCredentials reveals credential identifiers to guests, a guest can force the server to deliver the workspace secret to attacker infrastructure.

Defensive priority

Defenders should prioritize verifying exposure of TypeBot workspaces, especially those with guest members, and ensure they are running version 3.17.0 or later.

Recommended defensive actions

• Verify TypeBot workspace configurations to ensure only authorized members have access.
• Update TypeBot to version 3.17.0 or later.
• Monitor TypeBot workspaces for suspicious activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability was patched in version 3.17.0. Defenders should verify exposure, prioritize updates, and monitor workspaces for suspicious activity related to OpenAI-compatible API keys. The NVD entry and CVE record provide additional context on the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.