# CVE-2026-10861: MISP post-login open redirect via pre_login_requested_url

> An attacker can redirect authenticated MISP users to malicious external sites, facilitating phishing attacks and credential theft.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-9gjj-gmcx-6fhj

## What is CVE-2026-10861?

CVE-2026-10861 is a medium-severity vulnerability in Misp-Project Misp, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An open redirect vulnerability existed in MISP UsersController::routeafterlogin() because the value stored in the pre_login_requested_url session key was used as the post-login redirect destination without sufficiently enforcing that it was a local application path.

An unauthenticated remote attacker could craft a link that causes a victim to visit a trusted MISP instance and, after successful authentication, be redirected to an attacker-controlled external URL. This could be abused to increase the credibility of phishing attacks, redirect users to counterfeit login pages, or deliver attacker-controlled content from an untrusted domain. CWE-601 describes this weakness as accepting user-controlled input that specifies an external link and using it in a redirect, with phishing as a common consequence. 

The patch mitigates the issue by decoding and parsing the URL, rejecting URLs with a scheme, host, user component, missing or non-local path, and protocol-relative forms such as //example.com and /\example.com.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-10861 being exploited?

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

What it is: CVE-2026-10861 is a medium-severity vulnerability in Misp-Project Misp, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-10861 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-10861/ (Markdown: https://insights.sbomify.com/CVE-2026-10861/index.md)
```

## Sources

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

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