flowintel: Authorization Bypass Through User-Controlled Key (CVE-2026-133663)
Published Last modified Sources: EUVD, CVE.org
What is affected, what to do
Update flowintel to version 4.1.0.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.6
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
8.6
CVSS v4
Severity High on the scale from 0 to 10.
Source: EUVD, CVE.org
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 73.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.6 Methodology
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.6
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-639, CWE-862
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request.
Affected operations include:
- Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task
- Retrieving task assignees for a task belonging to a different case
- Editing or deleting timeline events and timeline event links belonging to another case
- Editing or removing case connectors belonging to another case
- Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case
The root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent.
Security impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows.
Affected versions: flowintel prior to 4.1.0
Source: ENISA EUVD, cvelistv5, CVE.org (MITRE), NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| flowintel | flowintel |
|
|
Vendors and products
Weakness classes (CWE)
CWE-639Authorization Bypass Through User-Controlled Key
Base
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Entry at MITRE CWE-639CWE-862Missing Authorization
Class
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Entry at MITRE CWE-862
References & sources
- github.comSecurity patchPatch, euvd
- NVD (NIST)vuln/detail/CVE-2026-133663euvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedCIRCL
CVSS V4.0: AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): exploitation: none known, automatable: yes
Weakness type: CWE-639, CWE-862
Description added or changed
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request. Affected operations include: - Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task - Retrieving task assignees for a task belonging to a different case - Editing or deleting timeline events and timeline event links belonging to another case - Editing or removing case connectors belonging to another case - Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case The root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent. Security impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows. Affected versions: flowintel prior to 4.1.0CVSS added —AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/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:XWeakness type (CWE) added —CWE-639Weakness type (CWE) added —CWE-862Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/133xxx/CVE-2026-133663.json">CVE-2026-133663</a>Reference added —https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60aeSSVC assessment added —{"role":"Supplier","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-20T10:47:07Z"}Source identifier: 5a6e4751-2f3f-4070-9419-94fb35b644e8
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-133663"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-133663.svg?lang=en" alt="CVE-2026-133663 – NEOSEC Intel" height="20"></a>