PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-86408 MISP CVE debrief

CVE-2026-86408 debrief based on the supplied source corpus. 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. 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.

Vendor
MISP
Product
Unknown
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-07
Original CVE updated
2026-09-07
Advisory published
2026-09-07
Advisory updated
2026-09-07

Who should care

Defenders and administrators of MISP systems should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify MISP versions and assess exposure to this vulnerability.

Why it matters

CVE-2026-86408 allows sensitive cryptographic keys to be accessed without proper authorization in MISP systems, requiring defenders to verify versions and assess exposure.

  • Potential unauthorized access to sensitive cryptographic keys
  • Need to verify MISP versions and assess exposure
  • Possible impact on event authorization and access control

Technical summary

Affected versions of MISP do not enforce parent-event visibility when serving cryptographic keys through CryptographicKeysController::view(). The fix adds parent_id and parent_type to the lookup and then enforces authorization through the associated event. This vulnerability allows sensitive cryptographic keys to be accessed without proper authorization in MISP systems, requiring defenders to verify versions and assess exposure. The upstream commit explicitly states that cryptographicKeys/view could return a protected event’s signing key to any authenticated user.

Defensive priority

Defenders should prioritize verifying MISP versions and assessing exposure, as the vulnerability allows sensitive cryptographic keys to be accessed without proper authorization.

Recommended defensive actions

  • Verify MISP versions and assess exposure
  • Restrict access to sensitive cryptographic keys
  • Implement additional authorization checks
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but evidence is limited to the official CVE Program record and NIST NVD detail page. The upstream commit explicitly states that cryptographicKeys/view could return a protected event’s signing key to any authenticated user. Version affected: ≤2.5.45. Defenders should verify MISP versions and assess exposure.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-86408 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-86408

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-86408 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-86408

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/MISP/MISP/commit/2edde619b

    5a6e4751-2f3f-4070-9419-94fb35b644e8

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.