# CVE-2026-56422: MISP Core: Mass Assignment and Object Re-ownership via Unvalidated Request Fields

> Authenticated users can modify or reassign objects belonging to others by injecting unvalidated identifiers into request payloads.

- **Severity:** Critical 9.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-mf7v-x7r6-fq57

## What is CVE-2026-56422?

CVE-2026-56422 is a critical missing authorization vulnerability in misp, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-56422?


## How do I fix CVE-2026-56422?

No fix has been published for CVE-2026-56422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56422 being exploited?

There is no known exploitation of CVE-2026-56422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56422 and fix it if it is affected.

What it is: CVE-2026-56422 is a critical missing authorization vulnerability in misp, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56422 in the wild and no public exploit code.

Affected product: misp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56422/ (Markdown: https://insights.sbomify.com/CVE-2026-56422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56422
- OSV: https://osv.dev/vulnerability/CVE-2026-56422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56422/
Summaries are generated and may contain mistakes; the official description above is the record.