CVE-2026-133667: flowintel DOM-based XSS via Timeline Autolinking, Search Highlighting, and Content-Type Confusion
flowintel contains multiple related flaws that allow an authenticated attacker to inject arbitrary HTML or script into pages viewed by other users.
- Timeline rendering: the timeline library's autolinking feature rewrote already-sanitised case notes and imported MISP attribute values into generated HTML link elements. Crafted text containing quote characters could break out of the generated attribute context, altering the surrounding markup and enabling script execution in the victim's browser.
- Search highlighting: the highlight injection logic used a regular expression to locate text between angle brackets and spliced <mark> elements into the resulting string. Because the pattern could match inside HTML attribute values, the rewrite could corrupt or inject content into attributes of already-sanitised markup, again leading to DOM-based cross-site scripting.
- Content-Type confusion: three analyser selection endpoints returned session-stored JSON strings with a text/html content type. A browser receiving such a response will parse and render the body as HTML, so any HTML or script embedded in the stored value is executed in the victim's context.
Preconditions: the attacker must be an authenticated user with the ability to create or import case content (notes, MISP attributes) containing specially crafted quote or angle-bracket sequences. The victim must subsequently open the affected case timeline, run a search, or request one of the selection endpoints.
Impact: successful exploitation yields DOM-based cross-site scripting in the victim's browser session, potentially allowing disclosure of case data, session manipulation, or execution of arbitrary actions under the victim's identity.
Affected versions: flowintel prior to 4.1.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
flowintelto a version that resolves this vulnerability.Fixed in 4.1.0
Event History
Frequently Asked Questions
What access does an attacker need?
The stated precondition is that the attacker is authenticated. The available information does not establish whether an unauthenticated attack path exists.
Which users are at risk of code execution in their browser?
Other users are exposed when they view attacker-controlled content through the affected timeline rendering or search highlighting paths, or when their browser renders HTML or script contained in JSON returned by the affected analyser-selection endpoints.
What data paths can carry the malicious content?
The affected timeline path includes case notes and imported MISP attribute values. The content-type issue involves session-stored JSON strings returned by three analyser-selection endpoints as text/html.