CVE-2026-133667 (GCVE-0-2026-133667)

Vulnerability from cvelistv5 – Published: 2026-11-20 10:58 – Updated: 2026-11-20 18:26
VLAI
Title
flowintel DOM-based XSS via Timeline Autolinking, Search Highlighting, and Content-Type Confusion
Summary
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.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-20 10:50 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 18:26 UTC
CWE
  • CWE-79 - Improper Neutralization of Input in Web Page ('Cross-site Scripting')
  • CWE-799 - Improper Control of Resources Identifiers
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
flowintel flowintel Affected: 0 , < 4.1.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-20 10:50
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch 5352fc62c6a6…
Confidence
medium
Commit Subject Patch SHA-256
5f745040d79d fix: [security] Timeline and search rendering preserve text 5352fc62c6a6…
Fix summary

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.

Patch summary

In case_history.js and timeline_view.js, an autolink: false property is added to each TimelineJS event object to suppress linkification. In smart-render.js, the previous regex-based string replacement (html.replace(/>([^<]*)</g, ...)) is replaced with a DOM TreeWalker that iterates text nodes, builds <mark> elements via document.createElement and textContent, and splices them into a DocumentFragment, preserving all existing attributes and entities. A new count_html_matches helper counts matches across text nodes. The plain-text fallback branches that performed raw regex replacement on escaped strings are removed. In misp_modules.py, a new _selected_json_response helper decodes the session value with json.loads, wraps it in jsonify, sets X-Content-Type-Options: nosniff, and returns a 400 JSON error on TypeError, ValueError, or RecursionError. The three get_*_selected endpoints are updated to call this helper instead of returning the raw session string.

CVSS rationale

AV:N – the application is a web service reachable over the network. AC:L – crafting quote-bearing text in case notes or MISP attributes is straightforward; no race or special timing is needed. AT:N – no active attack or prior compromise is required beyond normal authenticated use. PR:L – the attacker needs an authenticated account to create or import the malicious content (endpoints are login_required). UI:A – the victim must actively open the case timeline, run a search, or request a selection endpoint for the injected markup to execute. VC:L – XSS can expose case data, session tokens, or other sensitive information visible in the browser. VI:L – the attacker can modify displayed content or trigger actions in the victim's session. VA:N – no evidence of denial-of-service impact beyond the nested-JSON guard. SC:N – no cross-component or cross-origin impact is demonstrated. SI:L – other authenticated users viewing the same case could be affected by the stored malicious content. SA:N – no elevation of security authority is indicated.

Weakness rationale
  • CWE-79 All three sub-issues (autolinking rewriting sanitised HTML, regex-based highlight injection corrupting attributes, and serving JSON as text/html) result in attacker-controlled content being interpreted as HTML/JavaScript in the victim's browser, which is the defining characteristic of DOM-based XSS.
  • CWE-799 The content-type confusion (serving application/json data as text/html) is a secondary weakness that amplifies the XSS by causing the browser to parse the response body as HTML. This is a narrower, supporting CWE.
Attack pattern rationale
  • CAPEC-6 The primary exploitation path is client-side: attacker-controlled text (case notes, MISP values, search terms) is processed by JavaScript in the browser (TimelineJS autolinking, regex-based highlight injection) and the resulting DOM manipulation injects executable markup. The content-type confusion endpoint is a secondary vector but the dominant pattern is DOM-based script injection. CAPEC-6 is the closest standard attack pattern; the mapping is confident because the patch explicitly addresses client-side HTML rewriting of user-supplied content.
  • CAPEC-1 The three selection endpoints that returned session JSON as text/html could be leveraged as a reflected XSS vector if the session content is influenced by a prior request parameter. This is a secondary, less certain mapping; CAPEC-6 remains the primary pattern. Included because the content-type confusion path is a distinct mechanism from pure DOM manipulation.
Assumptions to verify
  • The affected_version field in the metadata is recorded as '0', which is treated as a placeholder meaning all versions prior to 4.1.0 are affected; no earlier version boundary is specified.
  • The CVSS PR:L assumes the attacker needs an authenticated account to create the malicious case content; if unauthenticated import paths exist, PR could be N.
  • The CVSS UI:A assumes the victim must navigate to the affected page; if the malicious content is auto-loaded in a dashboard or notification, UI could be N.
  • CAPEC-1 (Reflected XSS) is included as a secondary mapping for the content-type confusion path; the primary and more certain mapping is CAPEC-6 (DOM Based XSS).
  • The nested-JSON rejection (RecursionError guard) suggests a potential DoS vector via deeply nested JSON, but no separate DoS impact is scored because the primary vulnerability is XSS.
  • No public exploit or PoC is referenced; exploitation status is assumed to be 'none'.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 medium 6
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-10-30 11:49 UTC Fix developed Corrective change authored (5f745040d79d2f08d4a06512a91313c5a4eb346b): fix: [security] Timeline and search rendering preserve text https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch
  2. 2026-11-20 10:49 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133667",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T18:26:26.477604Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T18:26:39.347Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/analyzer/misp_modules.py",
            "app/static/js/case/case_history.js",
            "app/static/js/case/timeline_view.js",
            "app/static/js/components/smart-render.js"
          ],
          "product": "flowintel",
          "programFiles": [],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThan": "4.1.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "elhoim"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "flowintel contains multiple related flaws that allow an authenticated attacker to inject arbitrary HTML or script into pages viewed by other users.\n\n- Timeline rendering: the timeline library\u0027s 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\u0027s browser.\n\n- Search highlighting: the highlight injection logic used a regular expression to locate text between angle brackets and spliced \u003cmark\u003e 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.\n\n- 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\u0027s context.\n\nPreconditions: 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.\n\nImpact: successful exploitation yields DOM-based cross-site scripting in the victim\u0027s browser session, potentially allowing disclosure of case data, session manipulation, or execution of arbitrary actions under the victim\u0027s identity.\n\nAffected versions: flowintel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-6",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-6 DOM Based XSS"
            }
          ]
        },
        {
          "capecId": "CAPEC-1",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-1 XSS - Reflected"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 4.8,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "LOW",
            "userInteraction": "ACTIVE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:L/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-20T10:50:21Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-79",
              "description": "CWE-79 Improper Neutralization of Input in Web Page (\u0027Cross-site Scripting\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-799",
              "description": "CWE-799 Improper Control of Resources Identifiers",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T10:58:27.052Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "title": "flowintel DOM-based XSS via Timeline Autolinking, Search Highlighting, and Content-Type Confusion",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected_version field in the metadata is recorded as \u00270\u0027, which is treated as a placeholder meaning all versions prior to 4.1.0 are affected; no earlier version boundary is specified.",
                  "The CVSS PR:L assumes the attacker needs an authenticated account to create the malicious case content; if unauthenticated import paths exist, PR could be N.",
                  "The CVSS UI:A assumes the victim must navigate to the affected page; if the malicious content is auto-loaded in a dashboard or notification, UI could be N.",
                  "CAPEC-1 (Reflected XSS) is included as a secondary mapping for the content-type confusion path; the primary and more certain mapping is CAPEC-6 (DOM Based XSS).",
                  "The nested-JSON rejection (RecursionError guard) suggests a potential DoS vector via deeply nested JSON, but no separate DoS impact is scored because the primary vulnerability is XSS.",
                  "No public exploit or PoC is referenced; exploitation status is assumed to be \u0027none\u0027."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-6",
                    "rationale": "The primary exploitation path is client-side: attacker-controlled text (case notes, MISP values, search terms) is processed by JavaScript in the browser (TimelineJS autolinking, regex-based highlight injection) and the resulting DOM manipulation injects executable markup. The content-type confusion endpoint is a secondary vector but the dominant pattern is DOM-based script injection. CAPEC-6 is the closest standard attack pattern; the mapping is confident because the patch explicitly addresses client-side HTML rewriting of user-supplied content."
                  },
                  {
                    "capecId": "CAPEC-1",
                    "rationale": "The three selection endpoints that returned session JSON as text/html could be leveraged as a reflected XSS vector if the session content is influenced by a prior request parameter. This is a secondary, less certain mapping; CAPEC-6 remains the primary pattern. Included because the content-type confusion path is a distinct mechanism from pure DOM manipulation."
                  }
                ],
                "commit": "5f745040d79d2f08d4a06512a91313c5a4eb346b",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "elhoim"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N \u2013 the application is a web service reachable over the network. AC:L \u2013 crafting quote-bearing text in case notes or MISP attributes is straightforward; no race or special timing is needed. AT:N \u2013 no active attack or prior compromise is required beyond normal authenticated use. PR:L \u2013 the attacker needs an authenticated account to create or import the malicious content (endpoints are login_required). UI:A \u2013 the victim must actively open the case timeline, run a search, or request a selection endpoint for the injected markup to execute. VC:L \u2013 XSS can expose case data, session tokens, or other sensitive information visible in the browser. VI:L \u2013 the attacker can modify displayed content or trigger actions in the victim\u0027s session. VA:N \u2013 no evidence of denial-of-service impact beyond the nested-JSON guard. SC:N \u2013 no cross-component or cross-origin impact is demonstrated. SI:L \u2013 other authenticated users viewing the same case could be affected by the stored malicious content. SA:N \u2013 no elevation of security authority is indicated.",
                "fixSummary": "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.",
                "generatedAt": "2026-11-20T10:50:21.529700Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 6,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "5352fc62c6a6482c29f863cbf7a788fdb94c38d87b96d115294e35c697eeefc6",
                "patchSummary": "In case_history.js and timeline_view.js, an autolink: false property is added to each TimelineJS event object to suppress linkification. In smart-render.js, the previous regex-based string replacement (html.replace(/\u003e([^\u003c]*)\u003c/g, ...)) is replaced with a DOM TreeWalker that iterates text nodes, builds \u003cmark\u003e elements via document.createElement and textContent, and splices them into a DocumentFragment, preserving all existing attributes and entities. A new count_html_matches helper counts matches across text nodes. The plain-text fallback branches that performed raw regex replacement on escaped strings are removed. In misp_modules.py, a new _selected_json_response helper decodes the session value with json.loads, wraps it in jsonify, sets X-Content-Type-Options: nosniff, and returns a 400 JSON error on TypeError, ValueError, or RecursionError. The three get_*_selected endpoints are updated to call this helper instead of returning the raw session string.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "5f745040d79d2f08d4a06512a91313c5a4eb346b",
                    "date": "Fri, 30 Oct 2026 12:49:38 +0100",
                    "patchSha256": "5352fc62c6a6482c29f863cbf7a788fdb94c38d87b96d115294e35c697eeefc6",
                    "retrievedAt": "2026-11-20T10:49:45.815552Z",
                    "source": "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch",
                    "subject": "fix: [security] Timeline and search rendering preserve text"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T10:50:21Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Timeline and search rendering preserve text",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-79",
                    "rationale": "All three sub-issues (autolinking rewriting sanitised HTML, regex-based highlight injection corrupting attributes, and serving JSON as text/html) result in attacker-controlled content being interpreted as HTML/JavaScript in the victim\u0027s browser, which is the defining characteristic of DOM-based XSS."
                  },
                  {
                    "cweId": "CWE-799",
                    "rationale": "The content-type confusion (serving application/json data as text/html) is a secondary weakness that amplifies the XSS by causing the browser to parse the response body as HTML. This is a narrower, supporting CWE."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (5f745040d79d2f08d4a06512a91313c5a4eb346b): fix: [security] Timeline and search rendering preserve text",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch"
                    ],
                    "timestamp": "2026-10-30T11:49:38Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b.patch"
                    ],
                    "timestamp": "2026-11-20T10:49:45.815552Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20406"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133667",
    "datePublished": "2026-11-20T10:58:27.052Z",
    "dateReserved": "2026-11-20T10:58:25.195Z",
    "dateUpdated": "2026-11-20T18:26:39.347Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "cpes": [
                  "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
                ],
                "modules": [
                  "app/analyzer/misp_modules.py",
                  "app/static/js/case/case_history.js",
                  "app/static/js/case/timeline_view.js",
                  "app/static/js/components/smart-render.js"
                ],
                "product": "flowintel",
                "repo": "https://github.com/flowintel/flowintel",
                "vendor": "flowintel",
                "versions": [
                  {
                    "lessThan": "4.1.0",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "flowintel contains multiple related flaws that allow an authenticated attacker to inject arbitrary HTML or script into pages viewed by other users.\n\n- Timeline rendering: the timeline library\u0027s 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\u0027s browser.\n\n- Search highlighting: the highlight injection logic used a regular expression to locate text between angle brackets and spliced \u003cmark\u003e 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.\n\n- 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\u0027s context.\n\nPreconditions: 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.\n\nImpact: successful exploitation yields DOM-based cross-site scripting in the victim\u0027s browser session, potentially allowing disclosure of case data, session manipulation, or execution of arbitrary actions under the victim\u0027s identity.\n\nAffected versions: flowintel prior to 4.1.0."
          }
        ],
        "id": "CVE-2026-133667",
        "lastModified": "2026-11-20T19:18:49.787",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 4.8,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "LOW",
                "userInteraction": "ACTIVE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "ssvcData": {
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "Supplier",
                "timestamp": "2026-11-20T10:50:21Z",
                "version": "2.0.3"
              }
            },
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-133667",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T18:26:26.477604Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-20T11:18:35.123",
        "references": [
          {
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "url": "https://github.com/flowintel/flowintel/commit/5f745040d79d2f08d4a06512a91313c5a4eb346b"
          }
        ],
        "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-79"
              },
              {
                "lang": "en",
                "value": "CWE-799"
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}


Solutions

CNA · CIRCL
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.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.