Affected versions of MISP do not enforce parent-event visibility when serving cryptographic keys through CryptographicKeysController::view().
The vulnerable handler queried CryptographicKey directly using the supplied key ID and selected sensitive fields such as:
*
type
*
key_data
*
fingerprint
but did not fetch or authorize the associated parent event first.
The upstream commit explicitly states that cryptographicKeys/view could return a protected event’s signing key to any authenticated user.
The fix adds parent_id and parent_type to the lookup and then enforces authorization through the associated event using fetchSimpleEvent($user, parent_id). If the parent is not an Event, access is limited to site administrators.
Version affected: ≤2.5.45
References
| Link | Resource |
|---|---|
| https://github.com/MISP/MISP/commit/2edde619b | Patch |
Configurations
History
No history.
Information
Published : 2026-09-07 13:20
Updated : 2026-09-09 15:26
NVD link : CVE-2026-86408
Mitre link : CVE-2026-86408
CVE.ORG link : CVE-2026-86408
JSON object : View
Products Affected
misp-project
- misp
