MISP signature verification bypass in protected events
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
MISP's protected event signature check can be bypassed. An attacker positioned on the network between two MISP instances can remotely, without logging in, insert whitespace into JSON keys and identifier values, and the receiving instance still accepts the modified event as authentic, which lets the attacker change its meaning while undermining its integrity.
Written by a model
Original description
MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace("/\s+/", "", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic.
The vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide.
The fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster 'meta' keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133188 (MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133188 (entry last updated 2026-11-19):
Affected:
- misp misp: through 2.5.51
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133188 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133188 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/MISP/MISP/commit/d5a3e9900
- https://github.com/MISP/MISP/commit/18d0e9a77
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133188
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133188"}.Affected versions
- misp mispthrough 2.5.51
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133188 |
| Record | NVD · CVE-2026-133188 |
| Other links 2 | |
| Patch | GitHub · MISP/MISP · Commit d5a3e990 |
| Patch | GitHub · MISP/MISP · Commit 18d0e9a7 |
Questions about CVE-2026-133188
Is CVE-2026-133188 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133188?
misp: through 2.5.51.
Source: cve.now feed data
Related
- CVE-2026-127046MISP Modules Website Exposes External Tool API Keys in /external_tools/list Response
- CVE-2026-127016MISP Modules Website: Missing Authorization on External Tool Management Endpoints
- CVE-2026-132144MISP: Non-admin users can change login email under external authentication to capture a directory identity
- CVE-2026-133175MISP Missing Authorization in Sync Proposal Endpoints Allows Cross-Event Data Access and Modification
- CVE-2026-132645MISP Galaxy Import Authorization Bypass Allows Unauthorized Overwrite of Default and Other Organizations' Galaxies
- CVE-2026-132644MISP Galaxy Cluster Import Authorization Bypass Allows Cross-Organization Cluster Takeover
No corrections so far. Something wrong on this page? Report an error.