MikroTrick: chained MikroTik RouterOS SSH flaws exploited to hijack routers

CERT Polska has disclosed six vulnerabilities in MikroTik RouterOS and warned that two of them, chained together and named MikroTrick, are being actively exploited. On devices whose SSH service is reachable remotely, the chain gives an attacker full administrative control without authentication. MikroTik shipped fixes on 3 September 2026, but successful attacks had already been seen from at least 2 September.

Technical details

  • CVE-2026-67276 (CVSS 9.2): SSH authentication bypass. RouterOS did not compare the entire RSA public key, so an attacker who knew a username and the key’s public modulus could log in without the private key.
  • CVE-2026-86060 (CVSS 9.2): mishandling of usernames that start with a disallowed character in the SSH login flow, which results in a session with full administrator rights.
  • CVE-2026-67277 (CVSS 8.8): a bandwidth-test service flaw that allows unauthenticated kernel memory disclosure or a remote crash and restart.

The remaining issues affect X.509 certificate handling, the SSH client and WebFig. In a first for the company, MikroTik also sent a push notification to users of its mobile app.

Exposure

According to Shadowserver data cited in reporting, about 122,500 MikroTik devices exposed SSH to the internet as of 5 September, although the number actually vulnerable was not determined. Compromised MikroTik routers have long been recruited into proxy networks and DDoS botnets.

Recommendations

  • Upgrade RouterOS. CERT Polska notes that 7.24.2 and 7.23.4 contain an incomplete fix, so move to 7.24.3+ (stable), 7.23.6+ (long-term) or 6.49.21+ (v6).
  • Block SSH, WWW/WWW-SSL and the bandwidth-test server from all networks except trusted management ranges.
  • Hunt for log lines such as login failure for user -2 ... via ssh and user <name> added by ssh:-2@<ip>, an unexpected privileged account named ops, and connections from 82.192.72.4 or 103.102.31.18.
  • Check /system/device-mode/print for the Flagged marker, and review users, scripts, scheduler tasks, proxies and tunnels.
  • If compromise is suspected, preserve logs, factory-reset, rebuild from a trusted configuration rather than a full backup, and rotate all secrets.

Sources