CVE-2026-133665 (GCVE-0-2026-133665)
Vulnerability from cvelistv5 – Published: 2026-11-20 10:58 – Updated: 2026-11-20 18:26| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/144… | 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 10:47 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch
ee51a7b891c2… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
1445157891ad
|
fix: [security] Alert secrets and webhook logs stay | ee51a7b891c2… |
Fix summary
The vulnerability is remediated by enforcing role-based access control on data serialization and template rendering. Non-admin users are now restricted to receiving only public enable flags and do not have access to webhook URLs, secrets, or delivery logs. The shared alert serializer explicitly removes sensitive fields for non-admin users, ensuring that both the notification page and the alerts API preserve administrative diagnostics while protecting sensitive data from unauthorized access.
Patch summary
The patch modifies app/alerts/alerts_core.py and app/notification/notification.py. In alerts_core.py, the alerts_to_json function now checks if the user is an admin and removes the webhook_url field from the JSON response for non-admin users. In notification.py, the index route now checks the current user's admin status. For non-admins, it passes a restricted configuration object containing only public enable flags (CASE_CREATE_ALERT_ENABLED, WEBHOOK_ENABLED) instead of the full ConfigModule, and it passes an empty list for alert_logs instead of the actual log data. This ensures sensitive configuration and logs are not embedded in the template context for unauthorized users.
CVSS rationale
Attack Vector is Network (AV:N) as the application is web-based. Attack Complexity is Low (AC:L) as it requires only standard HTTP requests. Attack Requirements are None (AT:N). Privileges Required are Low (PR:L) as any authenticated non-admin user can exploit this. User Interaction is None (UI:N). Vulnerable Component Impact is None (VC:N) as the server itself is not compromised. Vulnerable Component Integrity is High (VI:H) because sensitive secrets and logs are exposed, which can lead to further compromise. Vulnerable Component Availability is None (VA:N). Subsequent Component Impact is None (SC:N, SI:N, SA:N) as the direct impact is limited to information disclosure within the vulnerable component, though downstream impacts are possible but not directly measured by the base vector.
Weakness rationale
- CWE-200 The application exposed sensitive configuration data (webhook URLs, secrets, logs) to authenticated users who did not have the necessary privileges to view them.
- CWE-862 The application failed to enforce authorization checks when serializing alert data and rendering the notification page, allowing non-admin users to access admin-only data.
Attack pattern rationale
- CAPEC-126 The attacker leveraged their authenticated non-admin role to access data (webhook secrets, logs) that was not properly restricted to the administrator role, despite the UI hiding the configuration form.
Assumptions to verify
- The affected version is assumed to be all versions prior to 4.1.0 based on the fixed_version metadata.
- The CAPEC mapping is based on the general pattern of accessing restricted functionality, as the specific attack vector is a standard HTTP request to an existing endpoint.
- The CVSS vector assumes that the exposure of secrets leads to a high impact on integrity of the vulnerable component, as these secrets can be used to impersonate the application or access other services.
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 |
10 | 11 | high | 3 |
- 2026-10-30 13:18 UTC Fix developed Corrective change authored (1445157891add7c04a63e0014cd96bf9802cac66): fix: [security] Alert secrets and webhook logs stay https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch
- 2026-11-20 10:47 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133665",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:25:43.144657Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:26:03.887Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/alerts/alerts_core.py",
"app/notification/notification.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 an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended for administrators only.\n\nThe notification page and alert API responses exposed sensitive fields, including webhook URLs, signing secrets, IMAP credentials, and delivery logs, in the initial data or JSON responses. Although the user interface hid the configuration form from non-admin users, the underlying data remained accessible via the page source or API endpoints. This exposure included historical webhook URLs that may contain active bearer tokens.\n\nAn attacker with a valid non-admin account could retrieve these credentials and logs, potentially leading to unauthorized access to notification services, impersonation of the application in webhook deliveries, or further lateral movement within the infrastructure.\n\nAffected versions: flowintel \u003c 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Accessing Functionality Not Properly Restricted by User Role"
}
]
}
],
"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": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"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:47:41Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T10:58:14.508Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66"
}
],
"solutions": [
{
"lang": "en",
"value": "The vulnerability is remediated by enforcing role-based access control on data serialization and template rendering. Non-admin users are now restricted to receiving only public enable flags and do not have access to webhook URLs, secrets, or delivery logs. The shared alert serializer explicitly removes sensitive fields for non-admin users, ensuring that both the notification page and the alerts API preserve administrative diagnostics while protecting sensitive data from unauthorized access."
}
],
"title": "flowintel Information Disclosure of Webhook Secrets and Logs to Non-Admin Users",
"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 is assumed to be all versions prior to 4.1.0 based on the fixed_version metadata.",
"The CAPEC mapping is based on the general pattern of accessing restricted functionality, as the specific attack vector is a standard HTTP request to an existing endpoint.",
"The CVSS vector assumes that the exposure of secrets leads to a high impact on integrity of the vulnerable component, as these secrets can be used to impersonate the application or access other services."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The attacker leveraged their authenticated non-admin role to access data (webhook secrets, logs) that was not properly restricted to the administrator role, despite the UI hiding the configuration form."
}
],
"commit": "1445157891add7c04a63e0014cd96bf9802cac66",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "Attack Vector is Network (AV:N) as the application is web-based. Attack Complexity is Low (AC:L) as it requires only standard HTTP requests. Attack Requirements are None (AT:N). Privileges Required are Low (PR:L) as any authenticated non-admin user can exploit this. User Interaction is None (UI:N). Vulnerable Component Impact is None (VC:N) as the server itself is not compromised. Vulnerable Component Integrity is High (VI:H) because sensitive secrets and logs are exposed, which can lead to further compromise. Vulnerable Component Availability is None (VA:N). Subsequent Component Impact is None (SC:N, SI:N, SA:N) as the direct impact is limited to information disclosure within the vulnerable component, though downstream impacts are possible but not directly measured by the base vector.",
"fixSummary": "The vulnerability is remediated by enforcing role-based access control on data serialization and template rendering. Non-admin users are now restricted to receiving only public enable flags and do not have access to webhook URLs, secrets, or delivery logs. The shared alert serializer explicitly removes sensitive fields for non-admin users, ensuring that both the notification page and the alerts API preserve administrative diagnostics while protecting sensitive data from unauthorized access.",
"generatedAt": "2026-11-20T10:47:41.692593Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 3,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 10
}
],
"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": "ee51a7b891c2ec45c5c6526b8a6ac91b2026442d6662c5e5888f49a807834861",
"patchSummary": "The patch modifies app/alerts/alerts_core.py and app/notification/notification.py. In alerts_core.py, the alerts_to_json function now checks if the user is an admin and removes the webhook_url field from the JSON response for non-admin users. In notification.py, the index route now checks the current user\u0027s admin status. For non-admins, it passes a restricted configuration object containing only public enable flags (CASE_CREATE_ALERT_ENABLED, WEBHOOK_ENABLED) instead of the full ConfigModule, and it passes an empty list for alert_logs instead of the actual log data. This ensures sensitive configuration and logs are not embedded in the template context for unauthorized users.",
"patchTruncated": false,
"patches": [
{
"commit": "1445157891add7c04a63e0014cd96bf9802cac66",
"date": "Fri, 30 Oct 2026 14:18:20 +0100",
"patchSha256": "ee51a7b891c2ec45c5c6526b8a6ac91b2026442d6662c5e5888f49a807834861",
"retrievedAt": "2026-11-20T10:47:11.460773Z",
"source": "https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch",
"subject": "fix: [security] Alert secrets and webhook logs stay"
}
],
"source": "https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T10:47:41Z",
"version": "2.0.3"
},
"subject": "fix: [security] Alert secrets and webhook logs stay",
"weaknessRationale": [
{
"cweId": "CWE-200",
"rationale": "The application exposed sensitive configuration data (webhook URLs, secrets, logs) to authenticated users who did not have the necessary privileges to view them."
},
{
"cweId": "CWE-862",
"rationale": "The application failed to enforce authorization checks when serializing alert data and rendering the notification page, allowing non-admin users to access admin-only data."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (1445157891add7c04a63e0014cd96bf9802cac66): fix: [security] Alert secrets and webhook logs stay",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66.patch"
],
"timestamp": "2026-10-30T13:18:20Z",
"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/1445157891add7c04a63e0014cd96bf9802cac66.patch"
],
"timestamp": "2026-11-20T10:47:11.460773Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20405"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133665",
"datePublished": "2026-11-20T10:58:14.508Z",
"dateReserved": "2026-11-20T10:58:12.873Z",
"dateUpdated": "2026-11-20T18:26:03.887Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/alerts/alerts_core.py",
"app/notification/notification.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 an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended for administrators only.\n\nThe notification page and alert API responses exposed sensitive fields, including webhook URLs, signing secrets, IMAP credentials, and delivery logs, in the initial data or JSON responses. Although the user interface hid the configuration form from non-admin users, the underlying data remained accessible via the page source or API endpoints. This exposure included historical webhook URLs that may contain active bearer tokens.\n\nAn attacker with a valid non-admin account could retrieve these credentials and logs, potentially leading to unauthorized access to notification services, impersonation of the application in webhook deliveries, or further lateral movement within the infrastructure.\n\nAffected versions: flowintel \u003c 4.1.0"
}
],
"id": "CVE-2026-133665",
"lastModified": "2026-11-20T19:18:49.563",
"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": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"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:47:41Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133665",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:25:43.144657Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-20T11:18:34.920",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-200"
},
{
"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.