1-minute read
What a defender needs to know
CISA added RouterOS CVE-2026-67279 to its Known Exploited Vulnerabilities catalog on September 25, with a September 28 action date. On affected builds, an SSH rekey can take an unauthenticated client into the connection protocol, where the server dispatches an exec request. CERT Polska says this permits file creation, overwrite and reconstruction in the RouterOS-managed namespace, including support files with configuration and diagnostic data. CISA says the flaw can chain with CVE-2026-86060, an SSH login-helper privilege flaw.
This differs from the username-and-public-key route covered in our earlier MikroTik article. Scope this path by SSH reachability and build, rather than using the earlier -2 login pattern as your only hunt. MikroTik says the default configuration blocks internet SSH and recommends restricting manually exposed SSH to trusted addresses or using a VPN such as WireGuard.
Install fixed RouterOS 6.49.21, 7.23.4, 7.24.2 or 7.25 beta 3 according to each device’s release channel. Remove untrusted SSH access and test from outside the trusted network; the SSH connection should fail while approved management still works. After upgrading, check the critical Flagged entry in the Log section and inspect unexpected users, scripts and configuration, including on unflagged devices. Match the installed version to the release channel before counting the router as fixed: RouterOS 7 long-term and stable have different first-fixed builds. If RouterOS marks a device Flagged, follow MikroTik’s Flagged-status guidance. Review previously exposed routers even after restricting SSH. Investigate suspicious changes before restoring ordinary service.