# CVE-2026-95698: MISP Path Traversal in OrgImgHelper findOrgImage via Crafted Organization Name

> Authenticated attackers can exploit path traversal in MISP to read arbitrary PNG or SVG files and probe file existence via crafted organization names.

- **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-24qr-3pqh-xghm

## What is CVE-2026-95698?

CVE-2026-95698 is a medium-severity path traversal 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

The findOrgImage method in MISP's OrgImgHelper constructs a filesystem path by concatenating a user-supplied organization identifier with a fixed image directory and a file extension, then calls file_exists() on the resulting path. The organization name field is attacker-controllable through event import, which sets Org.name. Because no validation was performed on the field value before path construction, an organization name containing directory traversal sequences (e.g., ../../etc/passwd) would cause the path to resolve outside the intended org-image directory. 

This yields two security impacts: 

 - an arbitrary file existence oracle, since file_exists() returns a boolean for any path the process can access.
 - an arbitrary file read limited to files with .png or .svg extensions, because the resolved filename is returned and subsequently rendered or served to the requesting user.

The vulnerability requires an authenticated user with the ability to create or import events that set the organization name.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-95698 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95698 is a medium-severity path traversal 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-95698 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-95698/ (Markdown: https://insights.sbomify.com/CVE-2026-95698/index.md)
```

## Sources

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

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