CVE-2026-133190: fallo de gravedad media en misp
MISP CryptographicKey: Revoked PGP Keys Still Validate Protected Event Signatures and Key Revocation Sync Is Ineffective
Publicada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 6.3epss 0.1%
MISP, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events. Two related defects allow a revoked PGP key to remain effective for signing and validating protected events.
First, the validateProtectedEvent() method in the CryptographicKey model iterates over the event's stored cryptographic keys to verify a PGP signature but does not check the revoked flag on each key. A key explicitly marked as revoked is still used to validate signatures, meaning an entity whose key has been revoked can continue to sign protected events and have them accepted by the MISP instance.
Second, the captureCryptographicKeyUpdate() method, responsible for synchronizing the key list when a sync user edits a protected event, contained a query bug (find('first') instead of find('all')) that caused only the first stored key to be considered. As a result, revocations of additional keys were never persisted, keys absent from the pushed list were not removed, and entries lacking an explicit fingerprint were mismatched and incorrectly deleted. Additionally, the revocation logic did not enforce the invariant that a revocation, once stored, is never lifted by subsequent pushes.
A third minor issue: a signed protected event submitted without any cryptographic keys triggered an unhandled 500 error rather than a proper rejection response.
Preconditions: the attacker must be an authenticated sync user with permission to add or edit protected events on the MISP instance. The impact is that revoked keys retain signing authority, key revocations propagated by sync partners are silently dropped, and the integrity of the protected-event trust chain is compromised. In a multi-instance MISP deployment, events signed by revoked keys can propagate to other instances, extending the integrity impact across the sync network.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Productos afectados
misp · mispCVEs relacionadas — misp
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-85216CRITICALMISP LDAP and LinOTP Authentication Bypass via Empty or Invalid CredentialsEPSS 0.9%CVE-2026-56446HIGHAuthenticated Remote Code Execution via Arbitrary NDJSON Error Log Path in MISPEPSS 0.7%CVE-2026-67178HIGHOpen Redirect in MISP Installer-Generated Apache ConfigurationEPSS 0.7%CVE-2026-56447CRITICALMISP remote code execution via arbitrary rdkafka configuration pathEPSS 0.6%CVE-2026-56422CRITICALMISP Core: Mass Assignment and Object Re-ownership via Unvalidated Request FieldsEPSS 0.6%CVE-2026-93295HIGHMISP Background Job Argument Injection via Console Path Switches Enables Remote Code ExecutionEPSS 0.6%