# CVE-2026-54394: MISP organisation logo path traversal allows retrieval of arbitrary PNG/SVG files

> An attacker can retrieve arbitrary PNG or SVG files from the server by exploiting a path traversal flaw in the organisation logo retrieval 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/U:Green`)
- **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:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-c4wp-7485-699w

## What is CVE-2026-54394?

CVE-2026-54394 is a medium-severity path traversal vulnerability in misp, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MISP contains a path traversal vulnerability in OrganisationsController::getOrgLogo. The vulnerable code builds organisation logo file paths using organisation-controlled fields such as id, name, and uuid without ensuring that the resolved file remains inside the intended APP/files/img/orgs/ directory. An attacker able to influence an organisation field, for example the organisation name, could use path traversal sequences to cause MISP to return arbitrary readable .png or .svg files from outside the organisation logo directory. The issue is fixed by resolving candidate paths with realpath() and verifying that they remain under the expected base directory before serving the file.

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

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


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

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

## Is CVE-2026-54394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54394 is a medium-severity path traversal vulnerability in misp, published on 12 Jun 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-54394 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-54394/ (Markdown: https://insights.sbomify.com/CVE-2026-54394/index.md)
```

## Sources

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

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