# CVE-2026-56424: Missing authorization in misp > Authenticated users can bypass ownership checks to modify or delete other organizations' data in MISP, compromising intelligence integrity. - **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:N/SA:N`) - **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-r3v6-qw6x-wf6h ## What is CVE-2026-56424? CVE-2026-56424 is a high-severity missing authorization vulnerability in Misp-Project Misp, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description MISP core contained multiple broken access-control flaws where authorization checks were performed against the wrong entity, or where ownership/editability checks were missing on write paths. In affected subsystems, a lower-privileged authenticated user with the relevant feature permission could cause the application to authorize one object but mutate another, or could modify objects that were merely visible rather than editable by the user’s organization. The affected paths included: * Event Reports tag removal: the route-authorized report could differ from the report ID used for tag detachment, enabling cross-organization tag removal from another event report * Collection Elements bulk deletion: bulk deletion authorized against a collection whose ID matched the collection-element row ID, rather than the element’s actual parent collection, enabling deletion of elements from collections the user did not own. * Analyst Data capture/update: nested analyst data updates could overwrite an existing record without applying the normal canEditAnalystData ownership check, enabling cross-organization overwrite of analyst data records. * Template Elements editing: editing authorized against a template whose ID matched the template-element ID, rather than the element’s actual parent template, enabling unauthorized edits to another organization’s template elements. * Decaying Model editing and mappings: write paths loaded models using view-scope access but did not verify edit ownership, enabling users to edit or remap visible models owned by another organization.  Successful exploitation could allow an authenticated user with subsystem-specific permissions to perform unauthorized cross-organization modifications or deletions of MISP data, resulting in integrity loss, unauthorized tampering with shared intelligence, and disruption of analyst workflows. Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-56424? It affects 1 product. Products: Misp-Project Misp. ## How do I fix CVE-2026-56424? No fix has been published for CVE-2026-56424 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-56424 being exploited? There is no known exploitation of CVE-2026-56424 in the wild and no public exploit code. ## Other vulnerabilities in Misp-Project Misp - [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8) - [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8) - [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8) - [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8) - [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-56424 and fix it if it is affected. What it is: CVE-2026-56424 is a high-severity missing authorization vulnerability in Misp-Project 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-56424 in the wild and no public exploit code. Affected product: Misp-Project 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-56424/ (Markdown: https://insights.sbomify.com/CVE-2026-56424/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56424 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56424 - OSV: https://osv.dev/vulnerability/CVE-2026-56424 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-56424/ Summaries are generated and may contain mistakes; the official description above is the record.