CVE-2026-86347
CVE-2026-86347 — MISP Missing Authorization on Template File Upload Allows Authenticated Disk Exhaustion
Affected versions of MISP allow any authenticated user to access TemplatesController::uploadFile() because the ACL entry for templates/uploadFile used the wildcard *. This bypasses the intended role restrictions applied to neighboring template-management operations. The upload handler accepts arbitrary content with only minimal checks and writes it into app/tmp/files/. A low-privileged or read-only user can therefore repeatedly upload files and consume server disk space without requiring perm_add or perm_template. The fix changes the ACL requirement from * to perm_add. The commit also rules out stronger impacts: uploaded files receive random names, path traversal/predictable overwrite is not available, the temporary directory is outside the web root, and the files are not directly served over HTTP. Therefore, the issue should not be described as arbitrary file overwrite, stored XSS, or RCE. Version affected: ≤2.5.45
Published Updated Sources: NVD, MISP (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.1
high
Remediation
The vendor's own words where we have them.
Upgrade MISP to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| MISP | MISP | 0 to <= 2.5.45 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Attack Complexity
Low
Attack Vector
Network
Privileges Req
Low
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.1 | CVSS 4.0 | high | — | — | MISP (CNA) |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-400 · Uncontrolled Resource Consumption
- DoS: Crash, Exit, or Restart
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- DoS: Resource Consumption (Other)
Mitigation: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
CWE-862 · Missing Authorization
- Read Application Data
- Read Files or Directories
- Modify Application Data
- Modify Files or Directories
Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Weakness & attack patterns
- CWE-862
- CWE-400Uncontrolled Resource Consumption
Inferred from the weakness class — not observed against this CVE.
- T1211Exploitation for Defensive Evasion
- T1542.002Pre-OS Boot: Component Firmware
- T1556Modify Authentication Process
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /uploadFile, /tmp/files/, /predictable.
- Prioritize edge telemetry for network-reachable MISP.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.1 (AV:N)
Sep 7, 2026 · NVD
Initial · CVE published
Sep 7, 2026 · NVD
CVE published by MITRE.
Sep 7, 2026 · SOCRadar CTI
References
1 on the record
- github.com/MISP/MISP/commit/8e8885971
Exploit, Third Party Advisory
Elsewhere on this site
- MISPevery CVE for this vendor
- Access Controlsame class
- CWE-862other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-86347 is MISP Missing Authorization on Template File Upload Allows Authenticated Disk Exhaustion, a high vulnerability affecting MISP from MISP. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-86347. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-86347. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.