- 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.
No advisories yet.
Solution
The vulnerability is remediated by eliminating the three injection paths: (1) autolinking is disabled on every timeline event so the library no longer rewrites sanitised HTML; (2) search and auto-highlight marks are now created by walking the DOM text nodes and setting textContent, which cannot alter existing attributes or split character entities; (3) the three selection endpoints now decode the stored JSON once, respond with application/json and X-Content-Type-Options: nosniff, and reject malformed or excessively nested payloads with a 400 JSON error, preventing the browser from interpreting the body as HTML.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | flowintel DOM-based XSS via Timeline Autolinking, Search Highlighting, and Content-Type Confusion | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-79 CWE-799 |
|
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T10:58:27.052Z
Reserved: 2026-11-20T10:58:25.195Z
Link: CVE-2026-133667
No data.
Status : Received
Published: 2026-11-20T11:18:35.123
Modified: 2026-11-20T11:18:35.123
Link: CVE-2026-133667
No data.
OpenCVE Enrichment
No data.