# CVE-2026-60124: MISP importModule missing authorization allows read-only users to modify events via misp_standard imports

> Read-only users can modify MISP events via import modules due to missing authorization checks, compromising data integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/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:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-frwx-j879-pmqv

## What is CVE-2026-60124?

CVE-2026-60124 is a medium-severity missing authorization vulnerability in misp, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authorization bypass in MISP’s EventsController::importModule() allowed authenticated users or read-only API keys with event view access to persist data to events they were not allowed to modify. When an import module returned results in the misp_standard format, the write path did not verify event modification rights before saving the module output. This could allow a view-only user to inject or alter event data, impacting the integrity of MISP event content. The issue was fixed by enforcing the same modification-rights check used by related module result handling paths before processing misp_standard imports.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-60124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60124 is a medium-severity missing authorization vulnerability in misp, published on 8 Jul 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-60124 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-60124/ (Markdown: https://insights.sbomify.com/CVE-2026-60124/index.md)
```

## Sources

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

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