
MikroTik Routers Hijacked Through SSH With No Password At All
Kai Tanner on MikroTik routers wide open over SSH, no password, no CVE, and no patch coming because there's nothing to patch.
Continue reading
Attackers are taking full administrative control of internet-facing MikroTik routers over SSH without credentials, and the exposure is a configuration default, not a zero-day.
Attackers are gaining full administrative control of MikroTik routers by reaching the device's Secure Shell service directly from the internet, according to The Hacker News reporting on the campaign. No password is required. The technique is not a novel exploit chain against a patched flaw; it is SSH left reachable on the public interface with no access-list restriction, which MikroTik's own hardening documentation has told operators to close for years. The distinction that matters here is between a vulnerability disclosure and a configuration audit finding. This one is the second kind, and it does not get a CVE number to make it easier to track.
An HKMA-regulated bank running MikroTik gear at a branch, ATM backhaul link, or vendor site inherits this as a Technology Risk Management Guideline finding, not a patch-Tuesday item: TRM's expectation that remote administrative interfaces sit behind network segmentation and are not internet-facing applies whether or not a CVE exists. The audit question is not "are we patched" but "which of our routers answer SSH on the WAN port right now," a question a vulnerability scanner tuned for CVE matching will not surface. CVE-2025-6205 and CVE-2026-16232 above are both authentication-bypass flaws in named products with KEV dates; this MikroTik campaign has no such anchor and is easier to miss for exactly that reason.
No vendor patch resolves this because there is no vulnerable code path to patch. The control that would have changed the outcome is a firewall rule restricting SSH access to a management VLAN, plus disabling the service entirely on units that do not need remote administration. A bank's network team should be running an external port scan against its own MikroTik fleet this week, not waiting on a MikroTik advisory that will not arrive.



