CVE-2026-133626 (GCVE-0-2026-133626)
Vulnerability from cvelistv5 – Published: 2026-11-20 08:52 – Updated: 2026-11-20 18:15| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/90b… | 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 08:43 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch
1aa2d65a4e08… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
90b822a0fca3
|
fix: [security] Bound CSV and JSON expansion when converting | 1aa2d65a4e08… |
Fix summary
The fix introduces bounds on table expansion: a maximum padded-cell count (50,000) and a maximum padding ratio (4x filled cells). When a CSV or JSON dataset would exceed these limits, the original content is preserved in a safely fenced code block instead of being rendered as a table. Additionally, nested JSON values in table cells are now serialized in compact form (no indentation), and the JSON fallback path uses the same safe fencing helper, preventing both quadratic cell expansion and indentation-based output inflation.
Patch summary
In app/utils/file_converter.py: added constants MAX_PADDED_TABLE_CELLS (50000) and MAX_PADDING_RATIO (4); added helper _table_too_sparse() to detect oversized sparse tables; added helper _fenced_content() that generates a code fence long enough to prevent fence-injection from user content; modified convert_csv_to_note() to short-circuit to fenced output when the table is too sparse; modified convert_json_to_note() to apply the same sparse check for arrays of objects; changed json.dumps(value, indent=2) to json.dumps(value) for nested values in table cells; replaced the JSON fallback json.dumps(data, indent=2) with _fenced_content(content, "json"). In doc/user-manual.md: added a note documenting the new sparse-data behavior.
CVSS rationale
AV:N - the file conversion is accessible over the network via the web application. AC:L - crafting a sparse CSV/JSON file is straightforward; no race conditions or special timing required. AT:N - no prior tampering with system data needed. PR:L - requires an authenticated user with access to a case to attach and convert a file. UI:N - the conversion is triggered by the attacker's own action (uploading and converting the file); no victim interaction needed. VC:N, VI:N - no confidentiality or integrity impact. VA:H - worker exhaustion can deny service to other users of the FlowIntel instance. SC:N, SI:N, SA:N - no secondary component impact is evidenced.
Weakness rationale
- CWE-400 The application does not bound the expansion of sparse CSV/JSON data into padded table cells, allowing a small input to trigger quadratic memory/CPU allocation and exhaust a worker. This is a classic uncontrolled resource consumption issue.
- CWE-770 The table rendering path allocates cells proportional to rows x max_cols without any upper bound, and JSON pretty-printing further inflates output. No limit or throttle was applied before the fix.
Attack pattern rationale
- CAPEC-10 The attacker supplies a crafted CSV or JSON file that, when processed by the conversion feature, causes the application to allocate an excessive number of table cells, exhausting worker resources. This is a direct match to application resource exhaustion via crafted input.
- CAPEC-124 The underlying mechanism is quadratic expansion: a file with N columns and M rows produces N*M padded cells. The attacker exploits the algorithmic complexity of the table-padding logic. This is a secondary, more specific mapping; CAPEC-10 is the primary match.
Assumptions to verify
- PR:L assumes the file-to-note conversion feature requires an authenticated user with case access; the patch does not explicitly state authentication requirements, but FlowIntel is a case-management tool where case operations are typically authenticated.
- VA:H assumes that exhausting a single worker has a meaningful availability impact on the service; if the deployment runs many redundant workers behind a load balancer, the practical impact could be lower.
- CAPEC-124 is included as a secondary mapping; the primary mechanism is unbounded allocation (CAPEC-10), and the quadratic complexity is the underlying cause rather than a separate attack pattern.
- The affected version range is taken from the explicit context (affected_version 0, fixed_version 4.1.0); the patch itself does not encode version boundaries.
- The _fenced_content helper also mitigates a potential Markdown fence-injection issue (a crafted backtick sequence in the file content could break out of the code block), but the primary vulnerability addressed is resource exhaustion.
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 |
8 | 11 | high | 5 |
- 2026-11-06 09:53 UTC Fix developed Corrective change authored (90b822a0fca35d33688730772b964b478c7fcde6): fix: [security] Bound CSV and JSON expansion when converting https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch
- 2026-11-20 08:42 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133626",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:15:29.296559Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:15:48.121Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/utils/file_converter.py"
],
"product": "flowintel",
"programFiles": [
"app/utils/file_converter.py"
],
"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 a resource exhaustion vulnerability in its file-to-note conversion feature. When a user converts an attached CSV or JSON file into a case note, the application renders the data as a Markdown table by padding every row to the maximum column count. A crafted file with a small number of filled cells but a very large number of columns (or keys) causes the application to allocate a quadratic number of padded table cells, potentially exhausting a worker process in memory or CPU.\n\nThe same issue affects nested JSON values rendered inside table cells, where pretty-printed indentation further inflates the output size.\n\nPreconditions:\n- An authenticated user with access to a case in FlowIntel\n- Ability to attach and convert a CSV or JSON file to a note\n\nImpact:\n- Denial of service: exhaustion of a worker process, potentially disrupting service for other users\n- No confidentiality or integrity impact\n\nAffected versions: FlowIntel prior to 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-10",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-10 Application Resource Exhaustion"
}
]
},
{
"capecId": "CAPEC-124",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-124 Resource Exhaustion via Algorithmic Complexity"
}
]
}
],
"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:N/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"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-20T08:43:07Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400 Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-770",
"description": "CWE-770 Allocation of Resources Without Limits or Throttling",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T08:52:28.073Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces bounds on table expansion: a maximum padded-cell count (50,000) and a maximum padding ratio (4x filled cells). When a CSV or JSON dataset would exceed these limits, the original content is preserved in a safely fenced code block instead of being rendered as a table. Additionally, nested JSON values in table cells are now serialized in compact form (no indentation), and the JSON fallback path uses the same safe fencing helper, preventing both quadratic cell expansion and indentation-based output inflation."
}
],
"title": "FlowIntel: Resource Exhaustion via Sparse CSV/JSON Table Expansion During File-to-Note Conversion",
"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": [
"PR:L assumes the file-to-note conversion feature requires an authenticated user with case access; the patch does not explicitly state authentication requirements, but FlowIntel is a case-management tool where case operations are typically authenticated.",
"VA:H assumes that exhausting a single worker has a meaningful availability impact on the service; if the deployment runs many redundant workers behind a load balancer, the practical impact could be lower.",
"CAPEC-124 is included as a secondary mapping; the primary mechanism is unbounded allocation (CAPEC-10), and the quadratic complexity is the underlying cause rather than a separate attack pattern.",
"The affected version range is taken from the explicit context (affected_version 0, fixed_version 4.1.0); the patch itself does not encode version boundaries.",
"The _fenced_content helper also mitigates a potential Markdown fence-injection issue (a crafted backtick sequence in the file content could break out of the code block), but the primary vulnerability addressed is resource exhaustion."
],
"capecRationale": [
{
"capecId": "CAPEC-10",
"rationale": "The attacker supplies a crafted CSV or JSON file that, when processed by the conversion feature, causes the application to allocate an excessive number of table cells, exhausting worker resources. This is a direct match to application resource exhaustion via crafted input."
},
{
"capecId": "CAPEC-124",
"rationale": "The underlying mechanism is quadratic expansion: a file with N columns and M rows produces N*M padded cells. The attacker exploits the algorithmic complexity of the table-padding logic. This is a secondary, more specific mapping; CAPEC-10 is the primary match."
}
],
"commit": "90b822a0fca35d33688730772b964b478c7fcde6",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N - the file conversion is accessible over the network via the web application. AC:L - crafting a sparse CSV/JSON file is straightforward; no race conditions or special timing required. AT:N - no prior tampering with system data needed. PR:L - requires an authenticated user with access to a case to attach and convert a file. UI:N - the conversion is triggered by the attacker\u0027s own action (uploading and converting the file); no victim interaction needed. VC:N, VI:N - no confidentiality or integrity impact. VA:H - worker exhaustion can deny service to other users of the FlowIntel instance. SC:N, SI:N, SA:N - no secondary component impact is evidenced.",
"fixSummary": "The fix introduces bounds on table expansion: a maximum padded-cell count (50,000) and a maximum padding ratio (4x filled cells). When a CSV or JSON dataset would exceed these limits, the original content is preserved in a safely fenced code block instead of being rendered as a table. Additionally, nested JSON values in table cells are now serialized in compact form (no indentation), and the JSON fallback path uses the same safe fencing helper, preventing both quadratic cell expansion and indentation-based output inflation.",
"generatedAt": "2026-11-20T08:43:07.422130Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 8
}
],
"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": "1aa2d65a4e08d2c447aea812aa20e4190cf65a5be1e6a751afaae121545e51f4",
"patchSummary": "In app/utils/file_converter.py: added constants MAX_PADDED_TABLE_CELLS (50000) and MAX_PADDING_RATIO (4); added helper _table_too_sparse() to detect oversized sparse tables; added helper _fenced_content() that generates a code fence long enough to prevent fence-injection from user content; modified convert_csv_to_note() to short-circuit to fenced output when the table is too sparse; modified convert_json_to_note() to apply the same sparse check for arrays of objects; changed json.dumps(value, indent=2) to json.dumps(value) for nested values in table cells; replaced the JSON fallback json.dumps(data, indent=2) with _fenced_content(content, \"json\"). In doc/user-manual.md: added a note documenting the new sparse-data behavior.",
"patchTruncated": false,
"patches": [
{
"commit": "90b822a0fca35d33688730772b964b478c7fcde6",
"date": "Fri, 6 Nov 2026 10:53:20 +0100",
"patchSha256": "1aa2d65a4e08d2c447aea812aa20e4190cf65a5be1e6a751afaae121545e51f4",
"retrievedAt": "2026-11-20T08:42:42.445428Z",
"source": "https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch",
"subject": "fix: [security] Bound CSV and JSON expansion when converting"
}
],
"source": "https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T08:43:07Z",
"version": "2.0.3"
},
"subject": "fix: [security] Bound CSV and JSON expansion when converting",
"weaknessRationale": [
{
"cweId": "CWE-400",
"rationale": "The application does not bound the expansion of sparse CSV/JSON data into padded table cells, allowing a small input to trigger quadratic memory/CPU allocation and exhaust a worker. This is a classic uncontrolled resource consumption issue."
},
{
"cweId": "CWE-770",
"rationale": "The table rendering path allocates cells proportional to rows x max_cols without any upper bound, and JSON pretty-printing further inflates output. No limit or throttle was applied before the fix."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (90b822a0fca35d33688730772b964b478c7fcde6): fix: [security] Bound CSV and JSON expansion when converting",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6.patch"
],
"timestamp": "2026-11-06T09:53: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/90b822a0fca35d33688730772b964b478c7fcde6.patch"
],
"timestamp": "2026-11-20T08:42:42.445428Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20366"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133626",
"datePublished": "2026-11-20T08:52:28.073Z",
"dateReserved": "2026-11-20T08:52:20.420Z",
"dateUpdated": "2026-11-20T18:15:48.121Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-133626",
"date": "2026-11-20",
"epss": "0.00397",
"percentile": "0.34815"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/utils/file_converter.py"
],
"product": "flowintel",
"programFiles": [
"app/utils/file_converter.py"
],
"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 a resource exhaustion vulnerability in its file-to-note conversion feature. When a user converts an attached CSV or JSON file into a case note, the application renders the data as a Markdown table by padding every row to the maximum column count. A crafted file with a small number of filled cells but a very large number of columns (or keys) causes the application to allocate a quadratic number of padded table cells, potentially exhausting a worker process in memory or CPU.\n\nThe same issue affects nested JSON values rendered inside table cells, where pretty-printed indentation further inflates the output size.\n\nPreconditions:\n- An authenticated user with access to a case in FlowIntel\n- Ability to attach and convert a CSV or JSON file to a note\n\nImpact:\n- Denial of service: exhaustion of a worker process, potentially disrupting service for other users\n- No confidentiality or integrity impact\n\nAffected versions: FlowIntel prior to 4.1.0"
}
],
"id": "CVE-2026-133626",
"lastModified": "2026-11-20T19:18:47.920",
"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:N/VA:H/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": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"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-20T08:43:07Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133626",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:15:29.296559Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-20T09:20:09.370",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/flowintel/flowintel/commit/90b822a0fca35d33688730772b964b478c7fcde6"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-400"
},
{
"lang": "en",
"value": "CWE-770"
}
],
"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.