CVE-2026-94401: MISP Arbitrary Local File Read and SSRF via MISP Export Upload
MISP has a file-handling vulnerability that could let certain authenticated users make the server read files or access internal network services.
When importing an XML file, MISP did not properly verify that the uploaded content was actually XML. Because of this, a user with permission to modify data could upload a file containing a local file path or a web address instead.
If a local file path was supplied, MISP could read that file from the server. If a URL was supplied, MISP could make a request to that address, including systems that may only be reachable from inside the organization’s network.
The vulnerability could therefore expose sensitive local files and allow unauthorized requests to internal services.
Exploitation required a valid MISP account with modify permissions, but no additional user interaction was needed.
Version affected: <2.5.47
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MISPto a version that resolves this vulnerability.Fixed in 2.5.47 - Configuration
In addMISPExportFile(), add a pre-parse validation that rejects any uploaded content that does not contain the XML document marker '<', so path/URL strings cannot reach the XML parser.
MISP (addMISPExportFile / Xml::build) pre-parse validation (XML marker check) = Reject uploaded content not containing '<' - Configuration
In addMISPExportFile(), pass an explicit readFile => false option to Xml::build() to disable any library behavior that would interpret user-supplied input as a file path or URL to read/fetch.
MISP (addMISPExportFile / Xml::build) Xml::build option readFile = false
Event History
Frequently Asked Questions
Who can exploit this issue?
Exploitation requires a valid MISP account with permission to modify data. No additional user interaction is required once that access is available.
Are default MISP deployments affected?
The available information identifies affected versions as earlier than 2.5.47, but does not state whether any particular default configuration enables or prevents exploitation. Exposure depends on whether authenticated users have modify permissions and can import XML files.
What can an attacker access through this vulnerability?
An authorized attacker may cause the MISP server to read local files by supplying a local file path, or make requests to URLs. The URL-based behavior can reach internal network services that may not be externally accessible.
How can we determine whether we are affected?
MISP versions earlier than 2.5.47 are affected. Review which accounts have modify permissions and whether they can perform XML imports, as those accounts meet the stated exploitation prerequisite.