# CVE-2026-133188: MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-387p-88j7-c273

## What is CVE-2026-133188?

CVE-2026-133188 is a medium-severity vulnerability in misp, published on 19 Nov 2026. 

### Official 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 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-133188?

It affects 1 product.


Products: Misp.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*` up to 2.5.51

## How do I fix CVE-2026-133188?

No fix has been published for CVE-2026-133188 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133188 being exploited?

There is no known exploitation of CVE-2026-133188 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133188 and fix it if it is affected.

What it is: CVE-2026-133188 is a medium-severity vulnerability in misp, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133188 in the wild and no public exploit code.

Affected product: 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-133188/ (Markdown: https://insights.sbomify.com/CVE-2026-133188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133188
- OSV: https://osv.dev/vulnerability/CVE-2026-133188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133188/
Summaries are generated and may contain mistakes; the official description above is the record.
