# CVE-2026-10863: MISP User-controlled order parameter in correlations over-correlation endpoint

> An authenticated attacker can manipulate database query ordering in MISP, potentially exposing data or enabling SQL injection via the over-correlation endpoint.

- **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-cr4f-6g54-5c3c

## What is CVE-2026-10863?

CVE-2026-10863 is a medium-severity SQL injection vulnerability in Misp-Project Misp, published on 4 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security issue was fixed in the correlations over-correlation endpoint where the order query parameter was accepted from user-controlled named request parameters. This allowed an authenticated user to override the server-defined ordering of over-correlating values. Depending on how the value was processed by the underlying data access layer, this could allow manipulation of database query ordering and potentially expose the application to unsafe query construction.

The patch removes order from the set of request-controlled parameters and instead sets the ordering server-side to occurrence desc after processing allowed user parameters.

Affected component:
app/Controller/CorrelationsController.php, overCorrelations()

Security impact:
An authenticated attacker could influence the ordering clause used by the over-correlations query. The direct impact appears limited to query manipulation unless further evidence confirms SQL injection or unauthorized data exposure through the manipulated ordering expression.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-10863 being exploited?

There is no known exploitation of CVE-2026-10863 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-10863 and fix it if it is affected.

What it is: CVE-2026-10863 is a medium-severity SQL injection vulnerability in Misp-Project Misp, published on 4 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10863 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-10863/ (Markdown: https://insights.sbomify.com/CVE-2026-10863/index.md)
```

## Sources

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

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