{"id":"CVE-2026-133188","state":"PUBLISHED","title":"MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers","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.\n\nThe 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.\n\nThe 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.","publishedAt":"2026-11-19T14:32:35.724Z","updatedAt":"2026-11-19T20:09:05.870Z","severity":{"score":6.9,"label":"Medium","version":"4.0","vector":"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","source":"CIRCL"},"assigner":"CIRCL","products":["misp misp"],"affected":[{"vendor":"misp","product":"misp","versions":[{"version":"0","status":"affected","lessThanOrEqual":"2.5.51","versionType":"semver"}],"cpes":["cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"],"modules":["app/Model/CryptographicKey.php","app/Controller/EventsController.php","app/Lib/Tools/ServerSyncTool.php","app/Model/Server.php","app/Controller/Component/RestResponseComponent.php"],"programFiles":[],"repo":"https://github.com/MISP/MISP"}],"references":["https://github.com/MISP/MISP/commit/d5a3e9900","https://github.com/MISP/MISP/commit/18d0e9a77"],"weaknesses":["CWE-347","CWE-345"],"ingestedAt":"2026-11-19T20:18:06.313Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/133xxx/CVE-2026-133188.json","commit":"b4b236992400fc27ce77701a3b368b1611f52239","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-133188","state":"PUBLISHED","datePublished":"2026-11-19T14:32:35.724Z","dateUpdated":"2026-11-19T20:09:05.870Z","assignerShortName":"CIRCL","assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateReserved":"2026-11-19T14:32:32.740Z"},"containers":{"cna":{"title":"MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers","descriptions":[{"lang":"en","value":"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.\n\nThe 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.\n\nThe 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."}],"affected":[{"vendor":"misp","product":"misp","versions":[{"version":"0","status":"affected","lessThanOrEqual":"2.5.51","versionType":"semver"}],"cpes":["cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"],"modules":["app/Model/CryptographicKey.php","app/Controller/EventsController.php","app/Lib/Tools/ServerSyncTool.php","app/Model/Server.php","app/Controller/Component/RestResponseComponent.php"],"programFiles":[],"repo":"https://github.com/MISP/MISP"}],"references":[{"url":"https://github.com/MISP/MISP/commit/d5a3e9900","name":"Security patch","tags":["patch"]},{"url":"https://github.com/MISP/MISP/commit/18d0e9a77","name":"Security patch","tags":["patch"]}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV4_0":{"version":"4.0","vectorString":"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","baseScore":6.9,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"format":"SSVC","scenarios":[{"lang":"en","value":"GENERAL"}],"other":{"type":"SSVC","content":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-19T14:26:06Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}]}}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-347","lang":"en","description":"CWE-347 Improper Verification of Cryptographic Signature","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-345","lang":"en","description":"CWE-345 Insufficient Verification of Data Authenticity","type":"CWE"}]}],"providerMetadata":{"shortName":"CIRCL","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateUpdated":"2026-11-19T14:32:35.724Z"},"x_gcve":[{"recordType":"advisory","extensions":{"bcp-05-x-01":{"ai_annotations":[{"scope":"record","gna_source":1,"tags":["ai-computer-assisted:llm-generated","ai-computer-assisted:classification"],"description":"Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.","ai_level":"generated","review_status":"full","models":[{"name":"qwen3.8:27b","gna_source":1,"source":"ollama","identifier":"qwen3.8:27b"}]}]},"bcp-05-x-02":{"x_patch2vuln":{"generator":"patch2vuln.py","generatedAt":"2026-11-19T14:26:06.814235Z","model":"qwen3.8:27b","source":"patch set (2 sources)","patchSha256":"b81058778949ad6e64fefc78c4a9806e7776068075a40a338d47eb1d26eafde6","patchTruncated":false,"commit":"18d0e9a77d0c1d790a1742d9d886bf033d303ac6","subject":"fix: [security] Protected events are signed over their exact","patches":[{"source":"https://github.com/MISP/MISP/commit/d5a3e9900.patch","sourceUrl":"https://github.com/MISP/MISP/commit/d5a3e9900.patch","patchSha256":"bd22e66a2c3212896f9b0c25657a4e3d2e47ff2ba6bd377d33b4b62b2c524e08","commit":"d5a3e9900708e409bc9c517c57aa819883ca879e","subject":"fix: [security] Protected events refuse signed data with","date":"Fri, 13 Nov 2026 12:25:34 +0100","retrievedAt":"2026-11-19T14:25:13.678489Z"},{"source":"https://github.com/MISP/MISP/commit/18d0e9a77.patch","sourceUrl":"https://github.com/MISP/MISP/commit/18d0e9a77.patch","patchSha256":"4340f1f4d2e8a9f0806650a0896c11c11533e3d6ec6df786707ecdf2fd8120a5","commit":"18d0e9a77d0c1d790a1742d9d886bf033d303ac6","subject":"fix: [security] Protected events are signed over their exact","date":"Tue, 17 Nov 2026 14:37:58 +0100","retrievedAt":"2026-11-19T14:25:13.961710Z"}],"confidence":"medium","assumptions":["The CAPEC-126 mapping is the closest available pattern; the CAPEC catalog lacks a more specific entry for signature-coverage gaps introduced by data normalization before signing.","CVSS PR:N assumes the attacker only needs a network relay position and does not require authentication to either MISP instance; if the deployment requires authenticated relay, PR would be elevated.","CVSS VI:H assumes that renaming JSON fields or altering timestamps in protected events constitutes a high integrity impact; if the specific deployment treats these fields as non-critical, VI could be L.","The affected version boundary (< 3.0.0) is inferred from the patch's version_compare logic; the exact last affected release is not stated in the patch.","The Galaxy cluster 'meta' key exclusion from the whitespace scan means whitespace in meta keys remains a residual (documented) limitation, not a vulnerability.","SSVC technical_impact is set to 'partial' as the attacker can only insert whitespace, not arbitrarily rewrite event content; if field renaming has critical downstream effects in a specific deployment, 'total' may be more appropriate.","The Co-Authored-By line credits an AI assistant (Claude Opus 5.5); inclusion as a remediation developer follows the explicit metadata but is atypical for CVE credit conventions."],"fixSummary":"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.","patchSummary":"Patch 1 (d5a3e9900) adds a private method __hasUnsignedWhitespace() to CryptographicKey that recursively scans decoded JSON for whitespace in string keys (excluding 'meta' sub-keys) and in values whose keys match identifier patterns (uuid, id, timestamp, distribution, date). validateProtectedEvent() now calls this check after a successful signature verification and returns false with a log entry if unsigned whitespace is found.\n\nPatch 2 (18d0e9a77) extends signWithInstanceKey() and verifySignature() with an $exact parameter that skips whitespace stripping. A new signatureHeaders() method selects the appropriate signature header(s) based on the peer's MISP version. EventsController, ServerSyncTool, and RestResponseComponent are updated to emit and consume the x-pgp-signature-v2 header. The signature_version field is injected into protected event bodies. Server.php passes the v2 header to validateProtectedEvent(). A new test file ProtectedEventExactSignatureTest.php (339 lines) covers acceptance, rejection, and","credits":[{"lang":"en","value":"ENISA","type":"reporter"},{"lang":"en","value":"iglocska","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"remediation developer"}],"cvssRationale":"AV:N: The attacker operates over the network, intercepting and modifying traffic between MISP instances. AC:L: Inserting whitespace characters into JSON is a simple, deterministic transformation requiring no special conditions. AT:N: The target does not need to be in a particular state; any protected event in transit is vulnerable. PR:N: The attacker does not require authentication to the MISP instance; a network relay position suffices. UI:N: No user interaction is required; the tampered event is processed automatically. VC:N: No confidentiality impact; the attack modifies data, not exposes it. VI:H: The attacker can rename JSON fields and alter identifier values (UUIDs, timestamps), changing the semantic meaning of protected events while the signature still validates. VA:N: No availability impact. SC:N, SI:N, SA:N: The impact is confined to the receiving MISP instance's data integrity; no cross-scope or availability effects are evidenced.","ssvc":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-19T14:26:06Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}]},"weaknessRationale":[{"cweId":"CWE-347","rationale":"The PGP signature was computed and verified over a whitespace-stripped representation of the JSON body rather than the exact bytes transmitted. This allowed an attacker to modify the data (by inserting whitespace into keys or identifiers) without invalidating the signature, constituting an improper verification of the cryptographic signature's coverage."},{"cweId":"CWE-345","rationale":"The signature verification mechanism did not fully ensure the authenticity of the received data because the normalization step (whitespace removal) created a gap between the signed representation and the actual data, allowing undetected modifications."}],"capecRationale":[{"capecId":"CAPEC-126","rationale":"The digital signature mechanism was implemented over a normalized (whitespace-stripped) representation of the data rather than the exact transmitted bytes. An attacker in a relay position exploits this by inserting whitespace into JSON keys or identifier values, which survives the normalization and thus the signature check. CAPEC-126 is the closest match; uncertainty exists because the CAPEC catalog does not have a more specific pattern for signature-coverage gaps introduced by data normalization."}],"draft":false,"modelComparison":{"selectedModel":"qwen3.8:27b","selectionMethod":"deterministic-consensus-v1","selectionNotice":"The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.","rankings":[{"model":"qwen3.8:27b","score":5,"agreementScore":11,"confidence":"medium","assumptionCount":7}],"potentialErrors":[]}}},"bcp-05-x-03":{"x_timeline":{"events":[{"type":"fix-developed","timestamp":"2026-11-13T11:25:34Z","description":"Corrective change authored (d5a3e9900708e409bc9c517c57aa819883ca879e): fix: [security] Protected events refuse signed data with","references":["https://github.com/MISP/MISP/commit/d5a3e9900.patch"],"id":"evt-fix-developed-1"},{"type":"fix-developed","timestamp":"2026-11-17T13:37:58Z","description":"Corrective change authored (18d0e9a77d0c1d790a1742d9d886bf033d303ac6): fix: [security] Protected events are signed over their exact","references":["https://github.com/MISP/MISP/commit/18d0e9a77.patch"],"id":"evt-fix-developed-2"},{"id":"evt-fix-available-1","type":"fix-available","timestamp":"2026-11-19T14:25:13.678489Z","description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","references":["https://github.com/MISP/MISP/commit/d5a3e9900.patch"]},{"id":"evt-fix-available-2","type":"fix-available","timestamp":"2026-11-19T14:25:13.961710Z","description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","references":["https://github.com/MISP/MISP/commit/18d0e9a77.patch"]}]}}},"vulnId":"gcve-1-2026-20342"}],"solutions":[{"lang":"en","value":"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."}],"impacts":[{"capecId":"CAPEC-126","descriptions":[{"lang":"en","value":"CAPEC-126 Exploiting Incorrectly Implemented Digital Signatures"}]}],"credits":[{"lang":"en","value":"ENISA","type":"reporter"},{"lang":"en","value":"iglocska","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"remediation developer"}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*","versionStartIncluding":"0","versionEndIncluding":"2.5.51"}]}]}]},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-11-19T20:08:55.828367Z","id":"CVE-2026-133188","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-11-19T20:09:05.870Z"}}]}}}