Skip to content
Threat Brief

← All advisories

CVE-2026-66885

Medium 6.8No known exploitationFix available

Livebook Teams identity callback lacks state binding, allowing login CSRF

Record last updated

CVSS score

6.8

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 15% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-352

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
livebook-devlivebookfrom 0.15.0 before 0.18.70.18.7CVE Program
livebook-devlivebookfrom 0.15.0 before 0.18.70.18.7CVE Program
livebook-devlivebookfrom 0.15.0-cuda12 before 0.18.7-cuda120.18.7-cuda12CVE Program
livebook-devlivebookfrom 0.19.0 before 0.19.90.19.9CVE Program
livebook-devlivebookfrom 0.19.0 before 0.19.90.19.9CVE Program
livebook-devlivebookfrom 0.19.0-cuda12 before 0.19.9-cuda120.19.9-cuda12CVE Program
livebook-devlivebook4380a411920531223088267ed1c0ad21f96ef660Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references