CVE-2026-133188: misp · Improper Verification of Cryptographic Signature
Affects mispSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium · fixed in 3.0 : update misp when convenient.
Data as of 19 Nov 2026, 14:51 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 6.9 |
|---|
- Patch
- Available – fixed in 3.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mispmisp | Affected
| Fixed in– |
GitHubmisppkg:github/mispOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in MISP version 3.0 and later. These versions implement a post-verification scan that rejects any protected event containing whitespace in JSON keys or identifier-like values, and use a new exact-byte signature scheme that signs the JSON body without whitespace normalization. Users should upgrade to MISP 3.0 or later to fully mitigate this issue. Older versions (up to 2.5.51) are vulnerable. No other mitigation is indicated.
Description
MISP versions up to 2.5.51 have a vulnerability in the cryptographic signature verification process for protected events. The flaw allows an attacker positioned on the network between MISP instances to inject whitespace into JSON keys or identifier values without invalidating the PGP signature, enabling modification of event content while still passing signature verification. This undermines the integrity of protected event synchronization. The issue affects event creation, editing, viewing, and server-to-server synchronization. The fix, introduced in MISP 3.0, adds a post-verification check rejecting whitespace in keys and identifiers and implements an exact-byte signature scheme to prevent whitespace normalization attacks while maintaining backward compatibility with older instances.