# CVE-2026-86342: MISP Freetext Feed Preview Improper Authorization Exposes Restricted Event and Feed Information

> Attackers can view restricted event correlations and feed metadata by bypassing access controls in the freetext feed preview feature.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/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:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-hx7m-vxj3-9qmx

## What is CVE-2026-86342?

CVE-2026-86342 is a medium-severity missing authorization vulnerability in Misp-Project Misp, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of MISP contain improper authorization checks in the freetext feed preview functionality. The preview performed correlation lookups against attributes from events without applying the requesting user's ACL, allowing restricted event correlations and associated event information to be exposed to users who could not otherwise access those events. The vulnerable queries were scoped only by attribute values and deletion status rather than MISP's event, organization, sharing-group, attribute, and object-level access controls.

The same preview functionality also returned cross-feed correlation information without properly restricting the feed list to feeds visible to the caller. This exposed metadata for feeds that were not marked lookup_visible; one affected response additionally included the configured feed URL even though that value was not required by the feature.

The fixes apply the caller's ACL to attribute correlation searches, remove feed URLs from correlation results, restrict cross-feed results according to feed visibility, and correct host-organization ID comparison so the authorization rules are applied consistently.

Version affected: ≤2.5.45

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-86342 being exploited?

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

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

## Sources

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

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