CVE-2026-56422 — MISP IDOR via Client-Controlled Object Identifiers in Save Paths
Multiple MISP core controllers and model capture paths accepted client-controlled request fields such as primary keys (id) and ownership/scope foreign keys (event_id, org_id, user_id, sharing_group_id, galaxy_cluster_uuid, organisation_uuid, and related nested object identifiers) without consistently stripping, pinning, or revalidating them against the server-authorized object. In affected paths, an authenticated user with access to one authorized object could submit crafted REST or form payloads that caused MISP to save data against a different object than the one checked by the authorization logic. Depending on the endpoint, this could allow object overwrite, object re-parenting, ownership transfer, unauthorized sharing-group scoping, event/object injection, proposal retargeting, or stored attacker-controlled content appearing in another user’s context. The fixes harden affected create/edit/import flows by stripping client-supplied primary keys on create-only saves, re-pinning route- or database-authorized identifiers before save operations, validating effective sharing-group scope, and adding field whitelists where ownership fields must never be editable. The initial broad fix also added a central CRUDComponent::edit() primary-key re-pin so payload-supplied IDs cannot redirect saves away from the already-authorized row. GitHub’s patch for 7acf8220c describes this central issue as CRUDComponent::edit() copying supplied fields, including a payload primary key, onto the loaded record, allowing CakePHP save() to update an arbitrary row unless the loaded ID is re-pinned.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (MISP MISP).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.4 | CVSS 4.0 | Critical | — | — | 5a6e4751-2f3f-4070-9419-94fb35b644e8 via NIST National Vulnerability Database |
| 9.4 | CVSS 4.0 | Critical | — | — | CIRCL via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: 5a6e4751-2f3f-4070-9419-94fb35b644e8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.60%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Analysis and videos
CVE-2026-56422: MISP IDOR via Client-Controlled Object Identifiers in Save Paths
CVE-2026-56422 affects several MISP core controllers and model capture paths, where client-supplied primary keys and ownership or scope foreign keys were not consistently pinned to the authorized object. An authenticated user with access to one object could, in affected paths, cause MISP to save data against a different object. The record reports a CNA CVSS 4.0 score of 9.4, no KEV listing, and no affected or fixed version ranges.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · misp/misp
- SSVC assessment updated
- Record published
- CVSS changed · 9.4
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
16 on the record
- github.com/MISP/MISP/commit/2cc26f38f3e85c594957899f09043d5193146607
- github.com/MISP/MISP/commit/8311427c2edd72a8341f0a65e1f11073d7ad9191
- github.com/MISP/MISP/commit/57433015815e59db5a1f11536f90920952cf3fcd
- github.com/MISP/MISP/commit/05aad418c57bb78e6b58a843d70d45de8f50db45
- github.com/MISP/MISP/commit/84bafe69f5d0ab7f811371c0801a613f271ebc0b
- github.com/MISP/MISP/commit/63aebc27a878233b9475c742985aaef909bc755b
- github.com/MISP/MISP/commit/ab9619dfa6cb5210fd20fb3b0b57006e4fc93916
- github.com/MISP/MISP/commit/3ff6bd9cfdab5d41b4667ea7298d88ffd6f3fcb8
- github.com/MISP/MISP/commit/58f637aaab4d133e72f1454ebb963191d96d3b78
- github.com/MISP/MISP/commit/bc182d55dde5686a36ca2eb88fe6c2adabb9fad9
- github.com/MISP/MISP/commit/c80a3533b3d787f45f5185a4621cc0f05b0cf2e5
- github.com/MISP/MISP/commit/025f711506850aadb69cde1b57e5e5d57628c87f
- github.com/MISP/MISP/commit/00b2e3dae56fa24ea750eb525cc4709b7e5bee85
- github.com/MISP/MISP/commit/634f1f87c295193486c08c2c7ba1fee8a7339baa
- github.com/MISP/MISP/commit/7acf8220cafac58bcfb362da37aca512fe4bb396
- github.com/MISP/MISP/commit/9341690e9b6dde7f0605edea5533e05ba7362e35
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-107278 MISP Object Sync Drops Objects and Attributes When Description Is Empty 8d
- Medium CVE-2026-107276 MISP Email OTP Race Condition Allows One-Time Password to Be Consumed by Multiple Concurrent Requests 8d
- High CVE-2026-107180 MISP: Forced TOTP Enrolment Bypassed via Non-Browser Request Types on otp_required Instances 8d
- Medium CVE-2026-107175 MISP Correlation Engine Fails to Refresh When Event Distribution or Sharing Group Changes 8d
- Medium CVE-2026-106513 MISP: Site-Admin Can Repoint Redis Workers to Attacker-Controlled Server via UI/API Configuration Change 9d
- Medium CVE-2026-104914 MISP: Soft-Deleted Attributes from Other Organizations Exposed via Attribute Search and Paginated View 13d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-56422 is "MISP IDOR via Client-Controlled Object Identifiers in Save Paths", rated Critical. It affects MISP (MISP); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.4 describes technical severity. EPSS 0.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.