# CVE-2026-95693: MISP Information Disclosure via Forged Upload Path

> Authenticated users can enumerate server files and types via forged upload paths, leaking filesystem layout without reading contents.

- **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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-f496-75v4-rv5q

## What is CVE-2026-95693?

CVE-2026-95693 is a medium-severity vulnerability in MISP, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In MISP, the EventReport::uploadPicture method in processed a caller-supplied tmp_name field by invoking file_exists(), mime_content_type(), and exif_imagetype() on the supplied path before verifying that the value was a genuine PHP upload via is_uploaded_file(). An authenticated user holding the perm_add permission could supply an arbitrary filesystem path as the tmp_name value. The application would then probe that path and return distinct validation error messages depending on whether the file existed, its MIME type, or its image format. By observing the differing error responses, an attacker could enumerate the existence of files at arbitrary paths on the MISP server and determine their type. 

This constitutes an information disclosure vulnerability: the server's filesystem layout and file types are leaked to any user with the perm_add role without requiring administrative access. 

The vulnerability does not allow reading file contents, writing files, or executing code, but it can aid further attacks by revealing sensitive file locations (e.g., configuration files, private keys, or other artifacts) present on the host.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-95693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95693 is a medium-severity vulnerability in MISP, published on 22 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-95693 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-95693/ (Markdown: https://insights.sbomify.com/CVE-2026-95693/index.md)
```

## Sources

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

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