TL;DR: Update MikroTik RouterOS to version 6.49.21 (Long-term), 7.23.4 (Long-term), or 7.24.2 (Stable) immediately; if patching is not possible, restrict or disable SSH access from untrusted networks and follow CISA's BOD 26-04 guidance.
What Is the Flaw?
CVE-2026-67279 is classified as an Improper Enforcement of Behavioral Workflow vulnerability (CWE-841) in MikroTik RouterOS. It carries a CVSS 3.1 score of 6.5 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, meaning it is network-reachable, requires low attack complexity, and needs no privileges or user interaction to exploit.
The root cause lies in how RouterOS handles the SSH connection protocol. When a client requests a rekey operation, RouterOS incorrectly advances to the connection phase of the SSH protocol—even if the client has never attempted user authentication. Because the server accepts this state transition, an unauthenticated client can open a session channel and send an exec request. The RouterOS SSH server then dispatches the requested command as though the session were legitimately authenticated.
The practical result is that a remote, unauthenticated attacker can create, overwrite, and reconstruct files within the RouterOS managed file namespace. Files reachable in this namespace include support files containing configuration and diagnostic data, making this more than a simple file-write primitive.
CISA's KEV entry further notes that this vulnerability can be chained with CVE-2026-86060 to achieve unauthenticated exploitation with potentially greater impact. Organizations should treat both CVEs as a combined risk surface.
Who and What Is Affected?
The vulnerability affects MikroTik RouterOS builds prior to the fixed versions listed by the vendor. According to NVD, the following releases contain the fix:
- 6.49.21 — Long-term release branch
- 7.23.4 — Long-term release branch
- 7.24.2 — Stable release branch
Any RouterOS installation running versions earlier than these on devices that expose SSH to untrusted networks should be considered at risk. MikroTik hardware is widely deployed across internet service providers, enterprise edge networks, branch offices, and managed service provider environments, meaning the potential exposure surface is broad.
Because the CVSS vector shows AV:N (network-accessible) and PR:N/UI:N (no privileges, no user interaction required), every device with SSH reachable from an untrusted network is a candidate target regardless of the complexity of the surrounding environment.
What Is the Impact?
The CVSS base score of 6.5 (Medium) reflects partial confidentiality and integrity impact (C:L/I:L) with no direct availability impact in its own right. However, the real-world consequences can exceed what the base score alone suggests:
- Configuration file exposure: Support files in the RouterOS managed file namespace may contain sensitive configuration and diagnostic data, including credentials, network topology details, and routing information.
- Configuration tampering: An attacker able to overwrite or reconstruct files could alter router behavior, redirect traffic, weaken security policies, or establish persistence.
- Chaining risk: CISA explicitly states this vulnerability can be chained with CVE-2026-86060, potentially elevating the combined impact to full unauthenticated exploitation of the device.
- No authentication required: The barrier to exploitation is exceptionally low—any network-reachable attacker can attempt to trigger the vulnerable SSH state machine behavior.
CISA added this vulnerability to the Known Exploited Vulnerabilities catalog on 2026-09-25, indicating that exploitation has been observed in the wild. Organizations should treat this with urgency consistent with CISA's BOD 26-04 prioritization guidance.
What Should You Do Right Now?
Apply the vendor-supplied patches as your first priority:
- Identify all MikroTik RouterOS devices in your environment and their current version.
- Update to 6.49.21 (Long-term), 7.23.4 (Long-term), or 7.24.2 (Stable) depending on your release track, following MikroTik's official upgrade documentation.
- If immediate patching is not feasible, restrict SSH access to management interfaces only, using firewall rules to allow SSH exclusively from trusted IP ranges or management VLANs.
- Consider disabling SSH and using an alternative management method (Winbox over a secured management network, for example) on any device that cannot be patched promptly.
- Review RouterOS managed files—particularly support files—for any unexpected modifications that could indicate prior exploitation.
- Address CVE-2026-86060 concurrently, as CISA notes the two vulnerabilities can be chained.
- Comply with CISA's BOD 26-04 patching timelines for known exploited vulnerabilities and consult CISA's Forensics Triage Requirements if you suspect compromise.
Primary sources to consult:
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-67279
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- MikroTik's official release notes and changelog for the patched versions.
How Continuous External Testing Surfaces This Exposure
Many organizations are unaware that SSH management ports on network devices are reachable from the internet or from unexpected network segments until an external scan reveals it. CVE-2026-67279 is a prime example of a vulnerability where the difference between being exposed and being protected comes down to knowing your external attack surface.
Continuous external testing helps in several concrete ways:
- Service discovery: Regular external network scanning identifies which of your IP ranges are running SSH-accessible MikroTik devices, including devices that may have been overlooked in asset inventories.
- Version fingerprinting: Banner analysis and protocol-level fingerprinting can flag RouterOS SSH services running on versions known to be vulnerable, enabling prioritized remediation before an attacker acts.
- Change detection: When new devices are added to the perimeter or firewall rules change—inadvertently exposing a management port—continuous scanning catches that exposure in near-real time rather than at the next scheduled audit.
- Chained vulnerability correlation: Where CVE-2026-67279 and CVE-2026-86060 are present on the same host, an external testing platform can flag co-located risk, mirroring the chaining concern raised by CISA.
- Validation after patching: Post-patch scanning confirms that updated devices are no longer presenting vulnerable SSH banners, closing the loop on remediation verification.
Because MikroTik routers frequently sit at the network edge—exactly where external testers probe first—this class of vulnerability is reliably surfaced by disciplined, recurring external assessment rather than point-in-time internal reviews alone.
Sources & further reading: NVD CVE-2026-67279 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: cert.pl, cert.pl, forum.mikrotik.com, forum.mikrotik.com. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need any credentials or prior access to exploit CVE-2026-67279?
No. The CVSS vector for this vulnerability is PR:N/UI:N, meaning no privileges and no user interaction are required. The flaw allows an unauthenticated client to bypass SSH authentication by triggering a rekey operation, after which the server opens a session channel and dispatches exec requests without ever validating the user's identity.
Is this vulnerability being actively exploited?
Yes. CISA added CVE-2026-67279 to the Known Exploited Vulnerabilities catalog on 2026-09-25, which indicates that exploitation has been observed. Organizations should follow CISA's BOD 26-04 guidance for prioritization and remediation timelines. Consult the CISA KEV catalog directly for the most current status.
What versions of MikroTik RouterOS are fixed?
According to NVD, the vulnerability is resolved in RouterOS 6.49.21 (Long-term release), 7.23.4 (Long-term release), and 7.24.2 (Stable release). Devices running any earlier version should be treated as vulnerable until updated.
What is CVE-2026-86060, and why does it matter here?
CISA's KEV entry states that CVE-2026-67279 can be chained with CVE-2026-86060 to achieve unauthenticated exploitation. The specific mechanics of CVE-2026-86060 are outside the scope of this advisory, but organizations should investigate and remediate both CVEs together rather than treating them in isolation.