CVE-2025-66384 File upload in MISP
High 8.2
Published
Updated
Check this codebase for CVE-2025-66384 and fix it if it is affected.
What it is: CVE-2025-66384 is a high-severity vulnerability in MISP, published on 28 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66384 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-2025-66384/ (Markdown: https://insights.sbomify.com/CVE-2025-66384/index.md)
An attacker can upload malicious files to MISP due to invalid validation logic, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-66384?
CVE-2025-66384 is a high-severity vulnerability in MISP, published on 28 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
app/Controller/EventsController.php in MISP before 2.5.24 has invalid logic in checking for uploaded file validity, related to tmp_name.
Weakness: CWE-684
Which versions are affected by CVE-2025-66384?
How do I fix CVE-2025-66384?
No fix has been published for CVE-2025-66384 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-66384 being exploited?
There is no known exploitation of CVE-2025-66384 in the wild and no public exploit code.
Sources
Also known as GHSA-863h-c4v7-h5fv.