AUGUST 16, 2026
Live Feed
Back to database
Case File

CVE-2026-66885

MEDIUM · CVSS 6.5 EPSS 0.16% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-05 · Last synced 2026-08-16

CyberRota Analysis

AI-Generated

A Cross-Site Request Forgery (CSRF) vulnerability in Livebook allows attackers to authenticate a victim's browser session under the attacker's identity when Livebook is configured with Livebook Teams. This flaw enables an attacker, who is a member of the same Livebook Teams organization, to manipulate the login flow, resulting in the victim unknowingly operating under the attacker's account, potentially exposing sensitive data and actions. Organizations using affected versions of Livebook (0.15.0 to 0.18.7 and 0.19.0 to 0.19.9) should prioritize patching this vulnerability to prevent unauthorized access and data exposure.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-66885
Severity
MEDIUM
CVSS
6.5
EPSS
0.16%
Exchange

Original NVD Description

Cross-Site Request Forgery (CSRF) vulnerability in livebook-dev livebook allows an attacker to authenticate a victim's browser session under the attacker's own Livebook Teams identity. When Livebook is configured to use Livebook Teams for identity, Livebook.ZTA.LivebookTeams.handle_request/4 in lib/livebook/zta/livebook_teams.ex handles the OAuth-style callback carrying a teams_identity marker and a code parameter. The clause exchanges that code for an access token and writes the token into the browser session without verifying any value that ties the callback to the browser session that started the login. No state or nonce is generated when the flow is initiated: Livebook.Teams.Requests.create_auth_request/1 in lib/livebook/teams/requests.ex sends an empty request body, so no per-attempt value is ever registered, and the callback clause has nothing to compare against. An attacker who holds membership in the same Livebook Teams organisation as the target instance can therefore begin the login flow themselves, retain the resulting authorization code without redeeming it, and induce a victim to open a crafted URL carrying that code. The victim's browser completes the exchange and the resulting session is bound to the attacker's identity rather than the victim's. The victim is not required to hold any particular privilege, and no credential belonging to the victim is involved. The vulnerability does not allow the attacker to authenticate as the victim. The consequence is that a user believes they are working in their own authenticated session while they are in fact operating as another identity. Work performed in that session is attributed to the attacker's account, and secrets, uploaded data, or notebook results the victim produces are exposed to the attacker rather than kept in the victim's own account. The authorization code must be redeemed within a short window after the login flow begins, which constrains the timing of the attack but not its feasibility. This issue affects livebook: from 0.15.0 before 0.18.7 and from 0.19.0 before 0.19.9.

Related CVEs

Other vulnerabilities affecting the same vendor(s)