CVE-2026-86060
Exploitation confirmed. First attested on 2026-09-05 by CISA-ADP, CISA KEV, GCVE · enisa-cnw-kev, GCVE · previdian.
- Published2026-09-05
- Fixed in7.24.2 · 7.23.4 · 6.49.21
- WeaknessCWE-88
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
RouterOS contains an argument-handling flaw in the SSH login path involving usernames that begin with a prohibited character, allowing for the trusted RouterOS policy mask to be changed, leading to privilege escalation. Exploitation requires an unauthenticated SSH session to reach the RouterOS login helper.This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)
Timeline
dates in UTCObserved activity
isMalicious corpus · updated 2026-10-27 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-86060?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-86060?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.24 | ≥ 7.24, < 7.24.2 | 7.24.2 | NVD |
| 7.x | ≥ 7.0, < 7.23.4 | 7.23.4 | NVD |
| 6.x | ≥ 6.0, < 6.49.21 | 6.49.21 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Mikrotik routeros to 7.24.2 · 7.23.4 · 6.49.21
- CISA’s required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.due 2026-09-13
Advisories and patches
- cert.plMitigation
- forum.mikrotik.comRelease Notes
- forum.mikrotik.comRelease Notes
- forum.mikrotik.comRelease Notes
- mikrotik.comVendor Advisory
Detection
read 2026-10-28 00:45 UTC- Nuclei template
- none so far ProjectDiscovery
- Proof-of-concept repositories
- 3 repositories, unverifiedbahirul/cve-2026-86060digiprosec/MicroTrickgagaltotal/CVE-2026-mikrotik-poc PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2026-09-10
- Patch Due Date
- 2026-09-13
- Ransomware Use
- Unknown
- Required Action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Sources
- CISA KEVKEV entry2026-09-10
- GCVEexploitation2026-09-05
- CISA-ADPSSVC decisionactive2026-09-10
- OpenCVESSVC decisionactive—
- CNACVSS 4.09.2read 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-88read 2026-10-23
- FIRST EPSSEPSS score6.4 %2026-10-26
- PoC-in-GitHubproof of concept3read 2026-10-28
- Exploit-DBdetectionread 2026-10-28
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-09-05
- Last Modified
- 2026-09-11
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-86060?
Is CVE-2026-86060 actively exploited?
What is the CVSS score for CVE-2026-86060?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.