# CVE-2026-95703: MISP OrganisationsController File Existence and Image-Type Oracle via Forged Upload tmp_name

> Authenticated site-admins can determine file existence and image types on the server via a file upload oracle in MISP.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-f4j8-7jmm-g7jj

## What is CVE-2026-95703?

CVE-2026-95703 is a medium-severity vulnerability in MISP, published on 22 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In MISP, the OrganisationsController::__uploadLogo method processed a caller-supplied tmp_name value with filesystem probes (file_exists, MIME type detection, EXIF reading) before verifying that the value corresponded to a genuine PHP file upload via is_uploaded_file. An authenticated site-admin user could supply an arbitrary server file path as the tmp_name parameter. The application would then probe that path and return distinct validation error messages depending on whether the file existed and what its image type was, effectively creating a file-existence and image-type oracle against the server filesystem.

The vulnerability requires site-admin privileges and does not allow arbitrary file read, code execution, or modification; the impact is limited to disclosure of whether a given path exists on the server and, for image files, their type.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-95703 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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