flowintel cross-site scripting in case timeline and search
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.0
- Who is exposed
- Not reported
Summary
flowintel contains several flaws that let an authenticated attacker on the network inject HTML or script into pages other users view. The attacker plants crafted text in case notes or imported MISP attributes, and it runs when a victim opens the case timeline, runs a search, or requests certain analyser selection endpoints. Successful exploitation enables DOM-based cross-site scripting in the victim's browser, potentially exposing case data, manipulating the session, or performing actions under the victim's identity.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: 4.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133667 (flowintel DOM-based XSS via Timeline Autolinking, Search Highlighting, and Content-Type Confusion), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133667 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133667 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133667 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133667
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133667"}.Affected versions
- flowintel flowintelfixed in 4.1.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133667 |
| Record | NVD · CVE-2026-133667 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit 5f745040 |
Questions about CVE-2026-133667
Is CVE-2026-133667 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133667?
flowintel: before 4.1.0.
Source: cve.now feed data
How do I fix CVE-2026-133667?
Upgrade to a fixed version: 4.1.0.
Source: cve.now feed data
Related
- CVE-2026-133663flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification
- CVE-2026-133847flowintel: Missing Authorization Check Allows Organization Admin to Edit Platform Admin Accounts via Browser Interface
- CVE-2026-133662flowintel Analyzer: Missing Authorization on Result Reads and Case/Task Writes (IDOR)
- CVE-2026-133848flowintel: Organization Admin Can Delete Platform Admin Accounts Due to Missing Privilege Hierarchy Check
- CVE-2026-133854flowintel: Information Disclosure of Classification Usage via Missing Access Control
- CVE-2026-133849flowintel: Insecure Direct Object Reference in Task Calendar Access Control
No corrections so far. Something wrong on this page? Report an error.