# CVE-2026-85221: MISP CurlClient TLS Peer Verification Disabled by Default Enables Man-in-the-Middle Attacks > Attackers can perform man-in-the-middle attacks on MISP HTTPS connections due to disabled TLS peer verification, exposing sensitive threat intelligence and credentials. - **Severity:** High 7.6 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 3 Sep 2026 - **Updated:** 3 Sep 2026 - **Also known as:** GHSA-37pq-fmvf-2fwx ## What is CVE-2026-85221? CVE-2026-85221 is a high-severity vulnerability in Misp-Project Misp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description MISP contains an improper TLS certificate validation vulnerability in CurlClient. The CurlClient::$verifyPeer property was not explicitly initialized and therefore defaulted to null. When passed to cURL, this value effectively disabled TLS peer verification unless the calling code explicitly enabled it. As a result, HTTPS connections made through affected CurlClient instances could accept certificates that were not issued by a trusted certificate authority. An attacker capable of intercepting or manipulating network traffic between a MISP instance and a remote HTTPS service could impersonate the remote endpoint and perform a man-in-the-middle attack. Successful exploitation could allow an attacker to observe sensitive information transmitted by MISP, including authentication material or exchanged threat intelligence, and to modify responses returned to the MISP instance. The impact depends on the functionality using CurlClient and the data exchanged with the remote service. The patch enables TLS peer verification by default while preserving explicit support for configured self-signed certificates. It also corrects the self-signed certificate handling in SyncTool so that peer verification is disabled only when no pinned CA certificate is configured. Weakness: CWE-295 (Improper Certificate Validation) ## Which versions are affected by CVE-2026-85221? It affects 1 product. Products: Misp-Project Misp. ## How do I fix CVE-2026-85221? No fix has been published for CVE-2026-85221 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-85221 being exploited? There is no known exploitation of CVE-2026-85221 in the wild and no public exploit code. ## Other vulnerabilities in Misp-Project Misp - [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8) - [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8) - [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8) - [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8) - [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-85221 and fix it if it is affected. What it is: CVE-2026-85221 is a high-severity vulnerability in Misp-Project Misp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-85221 in the wild and no public exploit code. Affected product: Misp-Project Misp. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-85221/ (Markdown: https://insights.sbomify.com/CVE-2026-85221/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85221 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85221 - OSV: https://osv.dev/vulnerability/CVE-2026-85221 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-85221/ Summaries are generated and may contain mistakes; the official description above is the record.