nday
CVE-2026-133190

MISP CryptographicKey: Revoked PGP Keys Still Validate Protected Event Signatures and Key Revocation Sync Is Ineffective

misp / misp

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

authentication bypass
CWE-287, stated by the CNA CIRCL and NVD, republishing 5a6e4751-2f3f-4070-9419-94fb35b644e8
remote, unauthenticated
AV:N, PR:N, UI:N in 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 (CVSS 4.0) from the CNA CIRCL
network
AV:N in 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 (CVSS 4.0) from the CNA CIRCL
no authentication required
PR:N in 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 (CVSS 4.0) from the CNA CIRCL
no user interaction
UI:N in 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 (CVSS 4.0) from the CNA CIRCL
stage
DIS
disclosed
cvss
6.3 MEDIUM v4.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-19T14:44Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: the attacker must evade or get around security measures such as ASLR or DEP, or obtain target-specific secrets
Attack requirements AT:N
None: success does not depend on how the target is deployed or running
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 4.0 vector from the CVE record, scored by the CNA CIRCL.

Event log

+DISdisclosed

CVE record published by CIRCL. CVSS 6.3, medium.

src cvelist · nday , observed live · raw
{
  "id": 484621,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-133190",
  "occurred_at": "2026-11-19T14:44:46.132Z",
  "observed_at": "2026-11-19T15:00:30.436713Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "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",
      "version": "4.0",
      "base_score": 6.3,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-11-19T14:52:11.814868Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-19T14:44:46.132Z",
    "assigner_short_name": "CIRCL"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.