EUVD-2026-53603Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-delivered CSRF requiring organizational membership (PR:L) and victim click (UI:R); scope change (S:C) applies as victim session crosses to attacker identity; confidentiality high, no integrity or availability impact.
Primary rating from Vendor (6b3ad84c-e1a6-4bf7-a703-f496b71e49db).
CVSS VectorVendor: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Session hijacking via OAuth CSRF in Livebook's Livebook Teams identity provider allows an organization-member attacker to bind a victim's browser session to the attacker's own Teams identity. Livebook versions 0.15.0 through 0.18.6 and 0.19.0 through 0.19.8 are affected when the Livebook Teams ZTA provider is configured, as the OAuth callback handler accepts any valid authorization code without verifying it was issued for the current browser session. The attacker cannot authenticate as the victim, but the victim unknowingly operates under the attacker's identity, exposing notebooks, secrets, and uploaded data to the attacker's account. No public exploit code has been identified and active exploitation has not been confirmed by CISA KEV.
Technical ContextAI
Livebook is an Elixir-based interactive notebook platform. The vulnerability resides in Livebook.ZTA.LivebookTeams.handle_request/4 (lib/livebook/zta/livebook_teams.ex), which processes the OAuth-style callback when Livebook Teams is configured as the Zero Trust Authentication provider. CWE-352 (Cross-Site Request Forgery) applies precisely because Livebook.Teams.Requests.create_auth_request/1 (lib/livebook/teams/requests.ex) sends an empty request body - no state or nonce is registered at flow initiation. The callback clause therefore has no per-session binding to verify, so it accepts any in-window authorization code regardless of which browser session originated the login. The fix, visible in commit 21c16168263275541a6e076d0c31852c40e09a18, introduces a cryptographically random state value stored in the session (valid_auth_state?/2 using Plug.Crypto.secure_compare/2), aligning with the standard OAuth 2.0 CSRF mitigation specified in RFC 6749 section 10.12. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N confirms the network delivery, low complexity, required organization membership (PR:L), and mandatory victim interaction.
RemediationAI
Upgrade Livebook to version 0.18.7 (for the 0.15.x-0.18.x branch) or 0.19.9 (for the 0.19.x branch), which introduce OAuth state-parameter validation in the callback handler. The fix is confirmed across three upstream commits: 21c16168263275541a6e076d0c31852c40e09a18, 33a052daa386c4ce08a9c39a07fc90f353ff6a51, and 6ed2e213e9d5a19a70d7fcad5a8d616622cd2084. The GitHub Security Advisory at https://github.com/livebook-dev/livebook/security/advisories/GHSA-pvvw-28fw-c6fg provides authoritative guidance. If immediate upgrade is not feasible, restrict network access to the Livebook instance to only fully trusted, verified organization members, reducing the pool of potential attackers; note this is a compensating control that does not eliminate the vulnerability, only limits who can exploit it. Alternatively, disabling the Livebook Teams ZTA provider and substituting another authentication mechanism removes this specific attack path entirely, at the cost of Teams-based identity integration.
Livebook is a web application for writing interactive and collaborative code notebooks. Rated critical severity (CVSS 9.
Untrusted JavaScript rendered in Livebook notebook outputs can escape the sandboxed cross-origin iframe and trigger sess
Full unauthenticated access to Livebook 0.19.7-0.19.9 is possible when a Livebook Agent or App Server's deployment group
Path traversal in Livebook's notebook import pipeline allows an attacker who supplies a crafted `.livemd` file to write
Remote command injection in livebook-dev Livebook's deployment setup command generator allows an authenticated high-priv
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today