CVE-2026-133849 (GCVE-0-2026-133849)
Vulnerability from cvelistv5 – Published: 2026-11-20 14:39 – Updated: 2026-11-20 16:34- CWE-639 - Authorization Bypass Through User-Controlled Key
| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/981… | 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 14:19 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b
618096dd6233… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
98196d0523d4
|
fix: [security] Recheck private case access in task calendars | 618096dd6233… |
Fix summary
The vulnerability is remediated by adding explicit case visibility checks to the task calendar queries. The fix ensures that tasks are only visible if the user has permission to view the parent case, in addition to being assigned to the task or belonging to the same organization. This prevents the disclosure of private case data in calendar views and ICS feeds.
Patch summary
The patch modifies the `_tasks_visible_to_user_query` and `_tasks_assigned_to_user_query` functions in `app/calendar/calendar_core.py`. It replaces the previous outer join and filter logic with subqueries for task assignment and organization membership. A new filter condition is added to ensure that the case is not private or that the user has membership in the case's organization. This enforces case-level access control in calendar task queries.
CVSS rationale
The vulnerability is exploitable over the network (AV:N) with low complexity (AC:L) and no attack requirements (AT:N). It requires low privileges (PR:L) as any authenticated user can trigger the issue. No user interaction is required (UI:N). The impact is high on integrity (VI:H) due to unauthorized disclosure of private case data, but no impact on confidentiality (VC:N) or availability (VA:N) of the primary system, and no secondary impacts (SC:N, SI:N, SA:N).
Weakness rationale
- CWE-639 The vulnerability allows access to resources (private case data) based on user-controlled inputs (task assignment or organization membership) without verifying the authorization context (case visibility). This is a classic authorization bypass where the application fails to enforce proper access controls on the parent resource.
Attack pattern rationale
- CAPEC-126 The vulnerability allows users to access private case data by interacting with calendar endpoints that do not properly enforce case-level authorization. While not a direct URL manipulation, the effect is similar to forced browsing where the application fails to restrict access to resources based on the user's privileges. The uncertainty lies in the specific mechanism, but the impact is unauthorized access to restricted data.
Assumptions to verify
- The CAPEC mapping is uncertain as the specific attack pattern is not explicitly detailed in the patch, but CAPEC-126 is the closest plausible match for unauthorized access to restricted data.
- The CVSS vector assumes that the primary impact is on integrity (VI:H) due to unauthorized disclosure, but confidentiality (VC:N) is marked as none based on the assumption that the data is not considered highly sensitive in this context. This may need adjustment based on the sensitivity of the case data.
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 | medium | 2 |
- 2026-11-17 08:41 UTC Fix developed Corrective change authored (98196d0523d4e1136014574ff0b526da1d92381b): fix: [security] Recheck private case access in task calendars https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b
- 2026-11-20 14:19 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133849",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T16:20:54.062814Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T16:34:40.179Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/calendar/calendar_core.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": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "A vulnerability exists in the flowintel application\u0027s calendar functionality that allows unauthorized access to private case data. The task calendar queries failed to enforce visibility checks on the parent case associated with tasks. Specifically, tasks assigned to a user or belonging to the user\u0027s organization were returned in calendar views (including browser and API ICS feeds) without verifying whether the user had permission to view the parent case. This allowed users to potentially discover and access details of private cases they were not authorized to view, leading to information disclosure.\n\nThe issue affected the default task visibility logic and the assigned-only task queries. The fix ensures that case visibility is rechecked in addition to task assignment or organization membership, preventing the exposure of private case data in calendar outputs.\n\nAffected versions: flowintel \u003c 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Forced Browsing"
}
]
}
],
"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-20T14:19:51Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639 Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T14:39:31.566Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b"
}
],
"solutions": [
{
"lang": "en",
"value": "The vulnerability is remediated by adding explicit case visibility checks to the task calendar queries. The fix ensures that tasks are only visible if the user has permission to view the parent case, in addition to being assigned to the task or belonging to the same organization. This prevents the disclosure of private case data in calendar views and ICS feeds."
}
],
"title": "flowintel: Insecure Direct Object Reference in Task Calendar Access Control",
"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 CAPEC mapping is uncertain as the specific attack pattern is not explicitly detailed in the patch, but CAPEC-126 is the closest plausible match for unauthorized access to restricted data.",
"The CVSS vector assumes that the primary impact is on integrity (VI:H) due to unauthorized disclosure, but confidentiality (VC:N) is marked as none based on the assumption that the data is not considered highly sensitive in this context. This may need adjustment based on the sensitivity of the case data."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The vulnerability allows users to access private case data by interacting with calendar endpoints that do not properly enforce case-level authorization. While not a direct URL manipulation, the effect is similar to forced browsing where the application fails to restrict access to resources based on the user\u0027s privileges. The uncertainty lies in the specific mechanism, but the impact is unauthorized access to restricted data."
}
],
"commit": "98196d0523d4e1136014574ff0b526da1d92381b",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "The vulnerability is exploitable over the network (AV:N) with low complexity (AC:L) and no attack requirements (AT:N). It requires low privileges (PR:L) as any authenticated user can trigger the issue. No user interaction is required (UI:N). The impact is high on integrity (VI:H) due to unauthorized disclosure of private case data, but no impact on confidentiality (VC:N) or availability (VA:N) of the primary system, and no secondary impacts (SC:N, SI:N, SA:N).",
"fixSummary": "The vulnerability is remediated by adding explicit case visibility checks to the task calendar queries. The fix ensures that tasks are only visible if the user has permission to view the parent case, in addition to being assigned to the task or belonging to the same organization. This prevents the disclosure of private case data in calendar views and ICS feeds.",
"generatedAt": "2026-11-20T14:19:51.561363Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 2,
"confidence": "medium",
"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": "618096dd62335667906e545842f94c0eadf5d9d9732f43bc5873d61306321c61",
"patchSummary": "The patch modifies the `_tasks_visible_to_user_query` and `_tasks_assigned_to_user_query` functions in `app/calendar/calendar_core.py`. It replaces the previous outer join and filter logic with subqueries for task assignment and organization membership. A new filter condition is added to ensure that the case is not private or that the user has membership in the case\u0027s organization. This enforces case-level access control in calendar task queries.",
"patchTruncated": false,
"patches": [
{
"commit": "98196d0523d4e1136014574ff0b526da1d92381b",
"date": "Tue, 17 Nov 2026 09:41:44 +0100",
"patchSha256": "618096dd62335667906e545842f94c0eadf5d9d9732f43bc5873d61306321c61",
"retrievedAt": "2026-11-20T14:19:18.380521Z",
"source": "https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b",
"subject": "fix: [security] Recheck private case access in task calendars"
}
],
"source": "https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T14:19:51Z",
"version": "2.0.3"
},
"subject": "fix: [security] Recheck private case access in task calendars",
"weaknessRationale": [
{
"cweId": "CWE-639",
"rationale": "The vulnerability allows access to resources (private case data) based on user-controlled inputs (task assignment or organization membership) without verifying the authorization context (case visibility). This is a classic authorization bypass where the application fails to enforce proper access controls on the parent resource."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (98196d0523d4e1136014574ff0b526da1d92381b): fix: [security] Recheck private case access in task calendars",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b"
],
"timestamp": "2026-11-17T08:41:44Z",
"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/98196d0523d4e1136014574ff0b526da1d92381b"
],
"timestamp": "2026-11-20T14:19:18.380521Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20417"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133849",
"datePublished": "2026-11-20T14:39:31.566Z",
"dateReserved": "2026-11-20T14:39:25.925Z",
"dateUpdated": "2026-11-20T16:34:40.179Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/calendar/calendar_core.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": "A vulnerability exists in the flowintel application\u0027s calendar functionality that allows unauthorized access to private case data. The task calendar queries failed to enforce visibility checks on the parent case associated with tasks. Specifically, tasks assigned to a user or belonging to the user\u0027s organization were returned in calendar views (including browser and API ICS feeds) without verifying whether the user had permission to view the parent case. This allowed users to potentially discover and access details of private cases they were not authorized to view, leading to information disclosure.\n\nThe issue affected the default task visibility logic and the assigned-only task queries. The fix ensures that case visibility is rechecked in addition to task assignment or organization membership, preventing the exposure of private case data in calendar outputs.\n\nAffected versions: flowintel \u003c 4.1.0"
}
],
"id": "CVE-2026-133849",
"lastModified": "2026-11-20T17:18:22.690",
"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-20T14:19:51Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133849",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T16:20:54.062814Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-20T15:17:53.137",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/flowintel/flowintel/commit/98196d0523d4e1136014574ff0b526da1d92381b"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-639"
}
],
"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.