{"api_version":"1","generated_at":"2026-11-20T19:06:10+00:00","cve":"CVE-2026-133648","urls":{"html":"https://cve.report/CVE-2026-133648","api":"https://cve.report/api/cve/CVE-2026-133648.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133648","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133648"},"summary":{"title":"Flowintel Disables TLS Certificate Verification for MISP and Mail Connections","description":"Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data.\n\nAffected connections include:\n- All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation)\n- SMTP STARTTLS connections used for sending email notifications\n- IMAP TLS connections used for fetching mail archives and testing connectivity\n\nAn attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could:\n- Capture MISP API keys and mail credentials (SMTP/IMAP passwords)\n- Read all threat intelligence data exchanged (events, attributes, objects, reports)\n- Inject or modify threat intelligence data returned to Flowintel\n\nThe vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints.\n\nAffected versions: Flowintel prior to 4.1.0.","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 11:18:33","updated_at":"2026-11-20 11:18:33"},"problem_types":["CWE-295","CWE-295 CWE-295 Improper Certificate Validation"],"metrics":[{"version":"4.0","source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","score":"9.9","severity":"CRITICAL","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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","data":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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","baseScore":9.9,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"9.9","severity":"CRITICAL","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":9.9,"baseSeverity":"CRITICAL","privilegesRequired":"NONE","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f","name":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133648","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133648","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"flowintel","product":"flowintel","version":"affected 4.1.0 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"The fix introduces a shared TLS utility module that enforces certificate and hostname verification by default for all MISP and mail connections. MISP clients now receive a proper SSL verification context instead of ssl=False, and IMAP/SMTP connections use a verified ssl.SSLContext. Operators may configure a private CA bundle path or explicitly disable verification (which fails closed on malformed input). The previous urllib3 warning suppression is removed, and upgrade documentation warns that previously accepted self-signed or mismatched certificates will now cause connection failures.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"elhoim","lang":"en"},{"source":"CNA","value":"David Cruciani","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/connectors/connectors_core.py","app/modules/notify_user/email.py","app/modules/receive_from/receive_misp_object.py","app/modules/send_to/misp_event.py","app/modules/send_to/misp_event_task.py","app/modules/send_to/misp_object_event.py","app/tools/tools_core.py","app/tools/validate_api.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 disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data.\n\nAffected connections include:\n- All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation)\n- SMTP STARTTLS connections used for sending email notifications\n- IMAP TLS connections used for fetching mail archives and testing connectivity\n\nAn attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could:\n- Capture MISP API keys and mail credentials (SMTP/IMAP passwords)\n- Read all threat intelligence data exchanged (events, attributes, objects, reports)\n- Inject or modify threat intelligence data returned to Flowintel\n\nThe vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints.\n\nAffected versions: Flowintel prior to 4.1.0."}],"impacts":[{"capecId":"CAPEC-119","descriptions":[{"lang":"en","value":"CAPEC-119 Man-in-the-Middle"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":9.9,"baseSeverity":"CRITICAL","privilegesRequired":"NONE","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]},{"format":"SSVC","other":{"content":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:15:55Z","version":"2.0.3"},"type":"SSVC"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-295","description":"CWE-295 Improper Certificate Validation","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T10:23:53.537Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f"}],"solutions":[{"lang":"en","value":"The fix introduces a shared TLS utility module that enforces certificate and hostname verification by default for all MISP and mail connections. MISP clients now receive a proper SSL verification context instead of ssl=False, and IMAP/SMTP connections use a verified ssl.SSLContext. Operators may configure a private CA bundle path or explicitly disable verification (which fails closed on malformed input). The previous urllib3 warning suppression is removed, and upgrade documentation warns that previously accepted self-signed or mismatched certificates will now cause connection failures."}],"title":"Flowintel Disables TLS Certificate Verification for MISP and Mail Connections","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'); the patch itself does not enumerate all prior releases.","CVSS VI:H assumes the attacker can successfully inject or modify threat intelligence data in transit; if the MISP API enforces additional integrity checks server-side, the practical integrity impact may be lower.","CAPEC-119 (Man-in-the-Middle) is selected as the closest standard attack pattern; the patch does not reference a specific CAPEC, and the attack could also be described under CAPEC-123 (Session Hijacking) or CAPEC-107 (Web Service Cross-Site Request Forgery) in a broader sense, but CAPEC-119 most directly matches the described on-path interception scenario.","The patch assumes MISP connector URLs use HTTPS; if an operator configures a plain HTTP MISP URL, TLS verification is not applicable and the vulnerability does not manifest in the same way.","PR:N assumes the attacker does not need any Flowintel account; the vulnerability is in the outbound connection from Flowintel to MISP/mail, not in Flowintel's own authentication."],"capecRationale":[{"capecId":"CAPEC-119","rationale":"The disabled certificate verification directly enables a classic man-in-the-middle attack: an on-path attacker presents a self-signed or rogue certificate, Flowintel accepts it without validation, and the attacker reads and modifies all traffic. CAPEC-119 is the closest standard attack pattern describing interception and modification of communications between two parties. The patch commit message explicitly references an 'on-path attacker' impersonating the server, confirming this mapping."}],"commit":"b8e257ab17632eb37c912485cbd78ee7514b764f","confidence":"high","credits":[{"lang":"en","type":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N - The attack is performed over the network by intercepting traffic between Flowintel and MISP/mail servers. AC:L - No special race conditions or complex setup are needed; the attacker only needs a network position on the path. AT:N - Flowintel is a server application; no active user on the target is required for the connection to be made. PR:N - The attacker does not need any credentials or account on Flowintel. UI:N - No user interaction is required. VC:H - All data in transit (API keys, mail credentials, full threat intelligence content) is readable by the attacker. VI:H - The attacker can modify or inject threat intelligence data returned to Flowintel. VA:N - No denial-of-service impact is indicated. SC:H - The MISP instance's data and the mail server's data are exposed to the attacker. SI:H - Forged or modified data can be injected into the MISP instance via the compromised channel. SA:N - No security authority impact is evident.","fixSummary":"The fix introduces a shared TLS utility module that enforces certificate and hostname verification by default for all MISP and mail connections. MISP clients now receive a proper SSL verification context instead of ssl=False, and IMAP/SMTP connections use a verified ssl.SSLContext. Operators may configure a private CA bundle path or explicitly disable verification (which fails closed on malformed input). The previous urllib3 warning suppression is removed, and upgrade documentation warns that previously accepted self-signed or mismatched certificates will now cause connection failures.","generatedAt":"2026-11-20T10:15:55.134458Z","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":"286e145e7697fc6bd5fcba49ad4998a8b621fa9a18f2b287ba3c344f26f06338","patchSummary":"Added new file app/utils/tls.py providing misp_ssl() and mail_ssl_context() helpers that read MISP_VERIFY_SSL and MAIL_VERIFY_SSL config values (default True) and return appropriate verification settings or SSL contexts. Replaced all ssl=False arguments in PyMISP constructor calls across 8 files with ssl=misp_ssl(). Replaced bare server.starttls() with server.starttls(context=mail_ssl_context()) and added ssl_context=mail_ssl_context() to IMAP4_SSL calls. Removed all urllib3.disable_warnings() calls. Added MISP_VERIFY_SSL and MAIL_VERIFY_SSL to the default config template. Added installation documentation for TLS configuration and upgrade notes. The _verify_setting() helper raises ValueError on invalid input, ensuring fail-closed behavior.","patchTruncated":false,"patches":[{"commit":"b8e257ab17632eb37c912485cbd78ee7514b764f","date":"Mon, 2 Nov 2026 15:48:58 +0100","patchSha256":"286e145e7697fc6bd5fcba49ad4998a8b621fa9a18f2b287ba3c344f26f06338","retrievedAt":"2026-11-20T10:15:19.966655Z","source":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f.patch","sourceUrl":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f.patch","subject":"fix: [security] Verify TLS certificates for MISP and mail"}],"source":"https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f.patch","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:15:55Z","version":"2.0.3"},"subject":"fix: [security] Verify TLS certificates for MISP and mail","weaknessRationale":[{"cweId":"CWE-295","rationale":"The application explicitly disabled TLS certificate verification by passing ssl=False to all MISP client connections and by using unverified SSL contexts for IMAP/SMTP. This is a textbook case of improper certificate validation where the client accepts any server certificate without verifying the chain or hostname."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (b8e257ab17632eb37c912485cbd78ee7514b764f): fix: [security] Verify TLS certificates for MISP and mail","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/b8e257ab17632eb37c912485cbd78ee7514b764f.patch"],"timestamp":"2026-11-02T14:48:58Z","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/b8e257ab17632eb37c912485cbd78ee7514b764f.patch"],"timestamp":"2026-11-20T10:15:19.966655Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20254"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133648","datePublished":"2026-11-20T10:23:53.537Z","dateReserved":"2026-11-20T10:23:51.984Z","dateUpdated":"2026-11-20T10:23:53.537Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 11:18:33","lastModifiedDate":"2026-11-20 11:18:33","problem_types":["CWE-295","CWE-295 CWE-295 Improper Certificate Validation"],"metrics":{"cvssMetricV40":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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","baseScore":9.9,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","ssvcData":{"timestamp":"2026-11-20T10:15:55Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"Supplier","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133648","Ordinal":"1","Title":"Flowintel Disables TLS Certificate Verification for MISP and Mai","CVE":"CVE-2026-133648","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133648","Ordinal":"1","NoteData":"Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data.\n\nAffected connections include:\n- All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation)\n- SMTP STARTTLS connections used for sending email notifications\n- IMAP TLS connections used for fetching mail archives and testing connectivity\n\nAn attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could:\n- Capture MISP API keys and mail credentials (SMTP/IMAP passwords)\n- Read all threat intelligence data exchanged (events, attributes, objects, reports)\n- Inject or modify threat intelligence data returned to Flowintel\n\nThe vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints.\n\nAffected versions: Flowintel prior to 4.1.0.","Type":"Description","Title":"Flowintel Disables TLS Certificate Verification for MISP and Mai"}]}}}