Skip to content
Threat Brief

← All advisories

CVE-2026-133188

Medium 6.9No known exploitationFix available

MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers

Record last updated

CVSS score

6.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-347, CWE-345

Patching and mitigation

Patch status
Fix available (source: CVE record (CIRCL))
Fix documented (source date)
Vendor solution
The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks.
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mispmispall versions up to and including 2.5.51Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by CIRCL

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (CIRCL)

    Source: CVE record (CIRCL) (opens in a new tab)

Vendor guidance and references