CVE-2026-86060: MikroTik RouterOS MikroTrick policy-mask privilege escalation
Tech GuruQuick Answer
CISA added CVE-2026-86060 to its Known Exploited Vulnerabilities catalog on 2026-09-10, confirming that exploitation has occurred. If you operate MikroTik RouterOS, identify the exact version and relevant configuration now, preserve security evidence, and follow the live vendor remediation. A KEV match does not prove your system was compromised, and installing an update does not rule out earlier exploitation.
Operator action
Upgrade RouterOS to a fixed release, ensure SSH is not reachable from untrusted networks, then inspect the Flagged state, logs, users, scripts, and configuration for unrecognized changes.
Last verified: 2026-09-17 UTC. CISA KEV snapshot version
2026.09.16. Recheck the live advisory before changing production.
Context
Status At A Glance
| Product scope | MikroTik — RouterOS |
|---|---|
| CVE | CVE-2026-86060 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-09-10 |
| Vendor severity | MikroTik calls the release an important security update but does not publish a severity label on the advisory. |
| CVSS | MikroTik does not publish a CVSS score on the September advisory. |
| Ransomware field | Unknown — this is not the same as No; CISA has not marked the field Known. |
| Forensic-triage field | Yes — CISA's record calls for forensic triage. |
| CWE | CWE-88 |
| Federal remediation date | 2026-09-13 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
MikroTik RouterOS Improper Neutralization of Argument Delimiters in a Command Vulnerability. MikroTik RouterOS contains an improper neutralization of argument delimiters in a command vulnerability which allows an attacker to change the trusted RouterOS policy mask, leading to privilege escalation. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.
Affected Scope
MikroTik RouterOS contains an improper neutralization of argument delimiters in a command vulnerability which allows an attacker to change the trusted RouterOS policy mask, leading to privilege escalation.
Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.
Steps
What To Do Now
- Confirm. Inventory every RouterOS asset and record its exact version, patch level, role, relevant configuration, and exposure.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live MikroTik advisory.
- Remediate. Upgrade RouterOS to a fixed release, ensure SSH is not reachable from untrusted networks, then inspect the Flagged state, logs, users, scripts, and configuration for unrecognized changes.
- Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
- Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.
Fixed Releases And Mitigation
Verified fixed release, patch level, or update guidance captured at the last check:
- RouterOS 7.25 beta 3
- RouterOS 7.24.2
- RouterOS 7.23.4
- RouterOS 6.49.21
Mitigation boundary: MikroTik advises blocking SSH from untrusted networks and using a VPN for management. This reduces exposure but does not replace the fixed RouterOS release.
A workaround, access restriction, or provider-side control reduces a described path; it does not necessarily remove vulnerable code or erase compromise.
Investigation And Recovery
MikroTik says fixed RouterOS checks for compromise and writes a critical Flagged log entry when detected. Even without Flagged state, MikroTik advises inspecting scripts, users, and configuration after upgrading. CISA marks forensic triage Yes.
When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.
Notes
Exploitation Evidence
Vendor statement: MikroTik's September advisory does not make a general active-exploitation claim; it describes the RouterOS Flagged compromise check. CISA added this CVE to KEV on 2026-09-10.
CISA statement: CVE-2026-86060 was added to KEV on 2026-09-10. The ransomware field is Unknown, and the forensic-triage field is Yes. These are separate signals.
Validation And Boundaries
This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.
Related TechGeeks Resources
- Security Hot Page
- All Security Notices
- What to Do When a Device Hits CISA KEV
- Router CVE Exposure, Version, and Mitigation Checklist
- IoT Firmware Update and End-of-Support Checklist
- Live Protect and Runtime Vulnerability Shielding
References
Wrap-Up
Record whether CVE-2026-86060 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.
Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.
