CVE-2026-133631 (GCVE-0-2026-133631)
Vulnerability from cvelistv5 – Published: 2026-11-20 09:10 – Updated: 2026-11-20 18:18| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/34d… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-20 09:04 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch
c2ffe93f6a63… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
34d151b8dceb
|
fix: [security] Keep note references and AI tooling within | c2ffe93f6a63… |
Fix summary
Three remediations are applied: (1) Note variable resolution now enforces an audience-based authorization check so that cross-case and cross-task references only expand when the destination case's assigned organisations can read the referenced case; (2) the chatbot API tool is restricted to an explicit allow-list of reviewed read-only and search operations, with administrative endpoints always blocked, path validation against injection and SSRF, and write operations gated behind an explicit CHATBOT_ALLOW_WRITES configuration flag; (3) AI report requests are delivered to the child process via a private anonymous temporary file on stdin instead of argv, keeping credentials and case content out of the process listing.
Patch summary
In note_variables.py, a new _audience_can_view() function verifies that the destination case's organisations are a subset of the referenced case's organisations before resolving cross-case or cross-task references; case_notes.py passes the resolved case object instead of a raw integer ID. In chatbot_core.py, a _chatbot_api_request() validator and a _READ_API_PATHS regex allow-list are added; unsupported methods, external URLs, path traversal, admin routes, and non-allow-listed operations are refused before the MCP call. In CaseCore.py, the subprocess invocation for AI reports is changed from passing URL, payload, and headers as argv to writing them as JSON into a tempfile.TemporaryFile and feeding it via stdin. A CHATBOT_ALLOW_WRITES flag is added to the default config, and documentation is updated in the installation and user manuals.
CVSS rationale
AV:N: FlowIntel is a network-accessible web application. AC:L: An authenticated user can craft note references or interact with the chatbot without special conditions. AT:N: No specific attack target is required. PR:L: A low-privilege authenticated user with access to a shared note or the chatbot is sufficient. UI:N: No victim interaction beyond normal use is needed. VC:H: Private case data (titles, notes, MISP objects, user data) is exposed to unauthorized viewers and external AI/MISP systems. VI:L: The chatbot can invoke state-changing endpoints, allowing limited data modification. VA:N: No availability impact is evidenced. SC:L: Sensitive data is forwarded to external AI (Ollama) and MISP instances. SI:N: No subsequent integrity impact is demonstrated. SA:N: No subsequent availability impact.
Weakness rationale
- CWE-862 Note variable resolution did not verify that the destination case's audience had read access to the referenced case, allowing an authenticated user to pull private data from cases they are not authorised to view.
- CWE-284 The chatbot API tool lacked an allow-list or restriction on which API endpoints the model could invoke, permitting access to administrative and state-changing routes.
- CWE-200 The Ollama bearer token and case content were passed as command-line arguments, visible in the local process table to any user on the host.
Attack pattern rationale
- CAPEC-126 The note variable resolution relied solely on the viewer's own privileges without checking the destination case's audience, effectively an incorrectly implemented authorization scheme. An attacker crafts cross-case references in a note they can view to exfiltrate data from cases outside their access scope. This is the closest CAPEC to the missing audience-based authorization check.
- CAPEC-12 The chatbot API tool was configured to permit unrestricted API calls without an allow-list, representing an application configuration error that exposes administrative and write endpoints to model-driven requests. The fix introduces a restrictive default configuration. This mapping is approximate; no CAPEC specifically covers LLM-driven API over-permissiveness.
Assumptions to verify
- The affected version range is inferred from the explicit context (affected_version 0, fixed_version 4.1.0); no specific prior version boundary is confirmed in the patch.
- PR:L assumes the attacker is an authenticated FlowIntel user with access to at least one shared or imported note and the chatbot interface; unauthenticated access is not evidenced.
- VI:L for the chatbot assumes CHATBOT_ALLOW_WRITES is disabled by default; if enabled, the integrity impact could be higher.
- SC:L assumes AI report data and MISP sends reach external systems; if the deployment is fully air-gapped, SC could be N.
- CAPEC-126 is the closest available pattern for the missing audience-based authorization; no CAPEC specifically models cross-entity reference resolution authorization gaps.
- CAPEC-12 is used for the chatbot over-permissiveness; no CAPEC specifically covers LLM-driven unrestricted API invocation.
- The credential-in-argv issue (CWE-200) is a local information exposure and may not be exploitable in containerized or single-user deployments; its contribution to the overall CVSS is minor.
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 |
5 | 11 | medium | 7 |
- 2026-11-03 10:53 UTC Fix developed Corrective change authored (34d151b8dceb1fea925b353f04a9483aba0a22b1): fix: [security] Keep note references and AI tooling within https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch
- 2026-11-20 09:03 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133631",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:17:51.923396Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:18:08.558Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/case/CaseCore.py",
"app/case/case_notes.py",
"app/chatbot/chatbot_core.py",
"app/utils/note_variables.py"
],
"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 security flaws in its note variable resolution, chatbot API tooling, and AI report generation.\n\n- Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user\u0027s privileges rather than the destination case\u0027s audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case\u0027s audience having granted read access.\n\n- The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model\u0027s instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints.\n\n- AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user.\n\nAffected versions: FlowIntel prior to 4.1.0."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Exploiting Incorrectly Implemented Authentication Schemes"
}
]
},
{
"capecId": "CAPEC-12",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-12 Application Configuration Error"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"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-20T09:04:05Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-284",
"description": "CWE-284 Improper Access Control",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T09:11:43.154Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1"
}
],
"solutions": [
{
"lang": "en",
"value": "Three remediations are applied: (1) Note variable resolution now enforces an audience-based authorization check so that cross-case and cross-task references only expand when the destination case\u0027s assigned organisations can read the referenced case; (2) the chatbot API tool is restricted to an explicit allow-list of reviewed read-only and search operations, with administrative endpoints always blocked, path validation against injection and SSRF, and write operations gated behind an explicit CHATBOT_ALLOW_WRITES configuration flag; (3) AI report requests are delivered to the child process via a private anonymous temporary file on stdin instead of argv, keeping credentials and case content out of the process listing."
}
],
"title": "FlowIntel Insecure Note Variable Resolution, Over-Permissive Chatbot API Access, and Credential Exposure in Process Arguments",
"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 range is inferred from the explicit context (affected_version 0, fixed_version 4.1.0); no specific prior version boundary is confirmed in the patch.",
"PR:L assumes the attacker is an authenticated FlowIntel user with access to at least one shared or imported note and the chatbot interface; unauthenticated access is not evidenced.",
"VI:L for the chatbot assumes CHATBOT_ALLOW_WRITES is disabled by default; if enabled, the integrity impact could be higher.",
"SC:L assumes AI report data and MISP sends reach external systems; if the deployment is fully air-gapped, SC could be N.",
"CAPEC-126 is the closest available pattern for the missing audience-based authorization; no CAPEC specifically models cross-entity reference resolution authorization gaps.",
"CAPEC-12 is used for the chatbot over-permissiveness; no CAPEC specifically covers LLM-driven unrestricted API invocation.",
"The credential-in-argv issue (CWE-200) is a local information exposure and may not be exploitable in containerized or single-user deployments; its contribution to the overall CVSS is minor."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The note variable resolution relied solely on the viewer\u0027s own privileges without checking the destination case\u0027s audience, effectively an incorrectly implemented authorization scheme. An attacker crafts cross-case references in a note they can view to exfiltrate data from cases outside their access scope. This is the closest CAPEC to the missing audience-based authorization check."
},
{
"capecId": "CAPEC-12",
"rationale": "The chatbot API tool was configured to permit unrestricted API calls without an allow-list, representing an application configuration error that exposes administrative and write endpoints to model-driven requests. The fix introduces a restrictive default configuration. This mapping is approximate; no CAPEC specifically covers LLM-driven API over-permissiveness."
}
],
"commit": "34d151b8dceb1fea925b353f04a9483aba0a22b1",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N: FlowIntel is a network-accessible web application. AC:L: An authenticated user can craft note references or interact with the chatbot without special conditions. AT:N: No specific attack target is required. PR:L: A low-privilege authenticated user with access to a shared note or the chatbot is sufficient. UI:N: No victim interaction beyond normal use is needed. VC:H: Private case data (titles, notes, MISP objects, user data) is exposed to unauthorized viewers and external AI/MISP systems. VI:L: The chatbot can invoke state-changing endpoints, allowing limited data modification. VA:N: No availability impact is evidenced. SC:L: Sensitive data is forwarded to external AI (Ollama) and MISP instances. SI:N: No subsequent integrity impact is demonstrated. SA:N: No subsequent availability impact.",
"fixSummary": "Three remediations are applied: (1) Note variable resolution now enforces an audience-based authorization check so that cross-case and cross-task references only expand when the destination case\u0027s assigned organisations can read the referenced case; (2) the chatbot API tool is restricted to an explicit allow-list of reviewed read-only and search operations, with administrative endpoints always blocked, path validation against injection and SSRF, and write operations gated behind an explicit CHATBOT_ALLOW_WRITES configuration flag; (3) AI report requests are delivered to the child process via a private anonymous temporary file on stdin instead of argv, keeping credentials and case content out of the process listing.",
"generatedAt": "2026-11-20T09:04:05.830413Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 7,
"confidence": "medium",
"model": "qwen3.8:27b",
"score": 5
}
],
"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": "c2ffe93f6a63b984f6d1a733093060b3def8170a7f47b9662ca137faa3a5d7e4",
"patchSummary": "In note_variables.py, a new _audience_can_view() function verifies that the destination case\u0027s organisations are a subset of the referenced case\u0027s organisations before resolving cross-case or cross-task references; case_notes.py passes the resolved case object instead of a raw integer ID. In chatbot_core.py, a _chatbot_api_request() validator and a _READ_API_PATHS regex allow-list are added; unsupported methods, external URLs, path traversal, admin routes, and non-allow-listed operations are refused before the MCP call. In CaseCore.py, the subprocess invocation for AI reports is changed from passing URL, payload, and headers as argv to writing them as JSON into a tempfile.TemporaryFile and feeding it via stdin. A CHATBOT_ALLOW_WRITES flag is added to the default config, and documentation is updated in the installation and user manuals.",
"patchTruncated": false,
"patches": [
{
"commit": "34d151b8dceb1fea925b353f04a9483aba0a22b1",
"date": "Tue, 3 Nov 2026 11:53:18 +0100",
"patchSha256": "c2ffe93f6a63b984f6d1a733093060b3def8170a7f47b9662ca137faa3a5d7e4",
"retrievedAt": "2026-11-20T09:03:27.928581Z",
"source": "https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch",
"subject": "fix: [security] Keep note references and AI tooling within"
}
],
"source": "https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T09:04:05Z",
"version": "2.0.3"
},
"subject": "fix: [security] Keep note references and AI tooling within",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "Note variable resolution did not verify that the destination case\u0027s audience had read access to the referenced case, allowing an authenticated user to pull private data from cases they are not authorised to view."
},
{
"cweId": "CWE-284",
"rationale": "The chatbot API tool lacked an allow-list or restriction on which API endpoints the model could invoke, permitting access to administrative and state-changing routes."
},
{
"cweId": "CWE-200",
"rationale": "The Ollama bearer token and case content were passed as command-line arguments, visible in the local process table to any user on the host."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (34d151b8dceb1fea925b353f04a9483aba0a22b1): fix: [security] Keep note references and AI tooling within",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch"
],
"timestamp": "2026-11-03T10:53:18Z",
"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/34d151b8dceb1fea925b353f04a9483aba0a22b1.patch"
],
"timestamp": "2026-11-20T09:03:27.928581Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20355"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133631",
"datePublished": "2026-11-20T09:10:23.474Z",
"dateReserved": "2026-11-20T09:10:21.313Z",
"dateUpdated": "2026-11-20T18:18:08.558Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/case/CaseCore.py",
"app/case/case_notes.py",
"app/chatbot/chatbot_core.py",
"app/utils/note_variables.py"
],
"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 security flaws in its note variable resolution, chatbot API tooling, and AI report generation.\n\n- Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user\u0027s privileges rather than the destination case\u0027s audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case\u0027s audience having granted read access.\n\n- The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model\u0027s instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints.\n\n- AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user.\n\nAffected versions: FlowIntel prior to 4.1.0."
}
],
"id": "CVE-2026-133631",
"lastModified": "2026-11-20T19:18:48.640",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"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": "LOW",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/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:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"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-20T09:04:05Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133631",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:17:51.923396Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-20T10:17:11.027",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-200"
},
{
"lang": "en",
"value": "CWE-284"
},
{
"lang": "en",
"value": "CWE-862"
}
],
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"type": "Secondary"
}
]
}
}
}
}
Solutions
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.