CVE-2026-80426: FiftyOne before 1.21.0 Stored Cross-Site Scripting via Unescaped Field Description
FiftyOne renders a dataset field's description as markup. The sidebar field-information component at app/packages/core/src/components/FieldLabelAndInfo/index.tsx passes the description string to React's dangerouslySetInnerHTML, and no layer between storage and render escapes or sanitises it; the neighbouring info values in the same component are rendered as React children and are escaped, so the description is the only raw path. A description is free-form text held in the dataset schema, so it persists in the database and travels with an exported or published dataset. Opening a dataset obtained from another party and hovering the field runs the stored markup in the application's origin. That origin is shared with the FiftyOne server, whose media route returns the contents of a caller-named absolute path and which is unauthenticated in the open-source server, so the injected script can read local files and reach the dataset and operator endpoints as the viewing user.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users who open a dataset obtained from another party are exposed if that dataset contains a field description with stored markup. The markup executes when the user hovers over the affected field information in the application.
What does an attacker need to exploit it?
An attacker needs to place malicious markup in a dataset field description and get a user to open the dataset and hover over the relevant field. No authentication is required by the vulnerability vector, but user interaction is required.
What could successful exploitation allow?
The injected script runs in the FiftyOne application's origin. Because that origin is shared with an unauthenticated media route that returns caller-named absolute-path contents, the script may read local files and access dataset and operator endpoints as the viewing user.
How can I determine whether a dataset may be affected?
Inspect dataset schema field descriptions, especially in datasets imported, exported, published, or received from another party. Field descriptions containing HTML or script-like markup should be treated as potentially malicious because descriptions are stored and rendered without escaping or sanitization in affected versions.
What can be done if upgrading is not immediately possible?
Do not open untrusted datasets in the affected application, and avoid hovering field-information elements for datasets whose field descriptions have not been reviewed. Remove or replace untrusted field descriptions before making datasets available to users.