CVE-2026-66885
Received Received - Intake

CSRF in Livebook Teams Identity Authentication

Vulnerability report for CVE-2026-66885, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-05

Last updated on: 2026-08-05

Assigner: EEF

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-05
Last Modified
2026-08-05
Generated
2026-08-06
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
livebook livebook From 0.15.0 (inc) to 0.18.7 (exc)
livebook livebook From 0.19.0 (inc) to 0.19.9 (exc)
livebook-dev livebook From 0.15.0 (inc) to 0.18.7 (exc)
livebook-dev livebook From 0.19.0 (inc) to 0.19.9 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Cross-Site Request Forgery (CSRF) vulnerability in Livebook where an attacker can trick a victim into using the attacker's Livebook Teams identity. The flaw occurs during the OAuth login flow where no state or nonce is generated to link the callback to the original session. An attacker can initiate a login, retain the authorization code, and craft a URL with that code to force the victim's browser to complete the login. The victim then operates under the attacker's identity without realizing it.

Detection Guidance

This vulnerability cannot be detected through standard network or system commands as it involves a logic flaw in the OAuth-style login flow. Monitor for unexpected session ownership changes or unauthorized identity bindings in Livebook Teams logs.

Impact Analysis

If you are a Livebook user, this vulnerability could cause you to unknowingly work under an attacker's identity. Any work you perform, including secrets, uploaded data, or notebook results, would be attributed to the attacker's account. This could lead to data exposure, unauthorized actions, or misattribution of your work.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles or HIPAA's privacy rules. If an attacker gains access to a victim's session, they could exfiltrate or manipulate data, resulting in compliance breaches. Organizations using Livebook must address this to maintain regulatory compliance.

Mitigation Strategies

Upgrade Livebook to a patched version (0.18.7, 0.19.9, or later). If immediate upgrade is not possible, disable Livebook Teams authentication until patched. Review session logs for suspicious identity changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-66885. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart