CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

MikroTik RouterOS

product · product:mikrotik-routeros

Coverage
2
first 2026-09-06 → last 2026-10-18
Latest activity
2026-10-10
MikroTik's long-term changelogs already carry the fix for a pre-auth RouterOS RCE; its notice still says…
Peak priority
critical
1 critical · 1 routine
Targets
technology
sectors: technology, telco, public-sector
Sources cited
12
7 hosts

Action items (4)

Do-now tasks recorded on the entries about MikroTik RouterOS, newest first. Check the date before acting on an older one.

  • Find every RouterOS device whose www or www-ssl service answers from a network you do not trust and upgrade it to the fixed build for its channel: 7.24 or later on v7 stable, 7.23.8 on v7 long-term, 6.49.23 on v6 long-term; where an upgrade has to wait, restrict www and www-ssl under IP > Services to trusted addresses or disable them and manage the router over WinBox, SSH or a VPN.
    2026-10-10CVE-2026-84411
  • Immediate action: CERT Polska has independent confirmation of ongoing, successful attacks against MikroTik RouterOS devices whose SSH service is reachable from the internet, running since at least 2026-09-02 and continuing as of publication. Update to 6.49.21, 7.23.4, 7.24.2 or 7.25beta3 immediately; where an update cannot land within hours, remove SSH, WWW/WWW-SSL and the bandwidth-test service from any interface reachable outside a trusted management network. After updating, check the system log for the compromise markers and the device's own "Flagged" status, and inspect the configuration for unrecognized users, scripts, scheduler tasks, proxies and tunnels regardless of what the Flagged check reports.
    2026-09-06CVE-2026-67276 +5
  • Update every MikroTik RouterOS device to 7.23.6 (long-term) or 7.24.3 (stable), not merely to 7.23.4 / 7.24.2 / 6.49.21: the earlier releases fix the exploited SSH chain but carried an incomplete fix for the RSA signature-validation flaw, which is closed only in 7.23.6 and 7.24.3; where SSH, WWW/WWW-SSL or the bandwidth-test service are reachable from outside a trusted management network and an immediate update is not possible, remove that reachability first.
    2026-09-06CVE-2026-67276 +5
  • After updating, check the system log for a device-compromise message and the /system/device-mode/print Flagged status, and audit the configuration for any user, script, scheduler task, proxy server or tunnel you do not recognize; the Flagged marker only catches known post-compromise traces and its absence does not clear a device.
    2026-09-06CVE-2026-67276 +5

Defender insights

What each entry about MikroTik RouterOS tells a defender to do, newest first.

2026-10-10ROUTINEMikroTik's long-term changelogs already carry the fix for a pre-auth RouterOS RCE; its notice still says pending

Exposure · detection

2026-09-06CRITICALexploitedCERT Polska confirms active exploitation of an unauthenticated SSH takeover chain against internet-exposed MikroTik RouterOS devices

Triage

Story timeline

  1. 2026-10-10CVE-2026-84411, MikroTik RouterOS: one unauthenticated request to the web management service can run code as root; fixed in 7.24 (v7 stable), 7.23.8 (v7 long-term) and 6.49.23 (v6 long-term) (CVSS 3.1 9.8)
    trending-vulnerabilitiesMikroTik's long-term changelogs already carry the fix for a pre-auth RouterOS RCE; its notice still says pending
  2. 2026-09-06CVE-2026-67279 / CVE-2026-86060, MikroTik RouterOS "MikroTrick": an SSH rekey-during- authentication state-confusion bypass chained with a crafted-username privilege escalation reaches unauthenticated full device takeover, actively exploited
    deep-diveCERT Polska confirms active exploitation of an unauthenticated SSH takeover chain against internet-exposed MikroTik RouterOS devices
ATT&CK techniques (6 across 6 tactics)

6 techniques observed across 2 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • PersistenceCreate Account: Local Account
  • Privilege EscalationExploitation for Privilege Escalation
  • Credential AccessAdversary-in-the-Middle
  • CollectionData from Local System · Adversary-in-the-Middle
  • ImpactEndpoint Denial of Service: Application or System Exploitation

Initial Access TA0001

T1190Exploit Public-Facing Application×2

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-10/cve-2026-84411-mikrotik-routeros-web-management-preauth-rce · 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Persistence TA0003

T1136.001Create Account: Local Account×1

Adversaries may create a local account to maintain access to victim systems. Local accounts are those configured by an organization for use by users, remote support, services, or for administration on a single system or service.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Privilege Escalation TA0004

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Credential Access TA0006

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Collection TA0009

T1005Data from Local System×1

Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Impact TA0040

T1499.004Endpoint Denial of Service: Application or System Exploitation×1

Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users. Some systems may automatically restart critical applications and services when crashes occur, but they can likely be re-exploited to cause a persistent denial of service (DoS) condition.

Evidence: 2026-09-06/mikrotik-routeros-mikrotrick-ssh-auth-bypass-privesc-chain · ATT&CK page ↗

Entries about MikroTik RouterOS (2)

2026-10-10 · view entry permalink →

ROUTINECVE-2026-84411updatedNATOA2

CVE-2026-84411, MikroTik RouterOS: one unauthenticated request to the web management service can run code as root; fixed in 7.24 (v7 stable), 7.23.8 (v7 long-term) and 6.49.23 (v6 long-term) (CVSS 3.1 9.8)

MikroTik's notice of 2026-10-06 describes an integer underflow in HTTP request body handling of the RouterOS web management service, the service behind WebFig on the www and www-ssl ports: a single specially crafted request sent without logging in could crash the service or let an attacker execute code on the router with full privileges, and MikroTik rates the flaw critical as CVE-2026-84411 (MikroTik, 2026-10-06). CISA's advisory ICSA-26-272-06 describes the same flaw as reachable before authentication, scores it CVSS 3.1 9.8 and records no known public exploitation reported to it (CISA, 2026-09-29). RouterOS versions before 7.24, v6 included, are affected on devices where the attacker can reach the web interface; 7.24 fixes the v7 stable channel (MikroTik, 2026-10-06), and MikroTik's changelogs list the fix in 7.23.8 for v7 long-term (dated 2026-10-08) and in 6.49.23 for v6 long-term (dated 2026-10-07), while its notice still shows both long-term releases as pending (MikroTik, 2026-10-08; MikroTik forum, 2026-10-09; MikroTik forum, 2026-10-09; MikroTik, 2026-10-06). BleepingComputer notes that hackers and botnet malware often target MikroTik flaws and recalls a recent CERT Polska warning of an exploit chain against devices with SSH exposed to the internet (BleepingComputer, 2026-09-30).

A single specially crafted HTTP request, sent without logging in, could crash the service or allow an attacker to execute code on the router with full privileges.

Note that in the default configuration the firewall already blocks the web interface from the internet, so a device with default firewall rules is only reachable from the local network.

v7 long-term - release pending

MikroTik

No known public exploitation specifically targeting this vulnerability has been reported to CISA at this time.

CISA

system - improve stability (includes CVE-2026-84411, CVE-2026-103903);

MikroTik (RouterOS 7.23.8 changelog) 2026-10-08

6.49.23 (2026-10-07):

MikroTik forum (6.49.23 long-term release announcement) 2026-10-09

7.23.8 [long-term] is released!

MikroTik forum (7.23.8 long-term release announcement) 2026-10-09
Correctionrun 2026-10-13T0256Z-inteltitleheadlinesummarycvessourcesevidencesourcing_noteactionsbody

Earlier text said the v7 long-term and v6 long-term releases were still pending, as MikroTik's notice of 2026-10-06 does; that was wrong. MikroTik's own changelogs show both had already shipped: RouterOS 6.49.23 (2026-10-07) lists the line "system - improve stability (includes CVE-2026-84411);" and 7.23.8 (2026-10-08) the line "system - improve stability (includes CVE-2026-84411, CVE-2026-103903);" (MikroTik, 2026-10-08; MikroTik forum, 2026-10-09; MikroTik forum, 2026-10-09). The notice itself was unchanged when read on 2026-10-13 and still reads "v7 long-term - release pending" (MikroTik, 2026-10-06). Owners of long-term and v6 devices can therefore upgrade rather than only restrict the web service.

Correctionrun 2026-10-18T1307Z-auditevidencebody

The correction of 2026-10-13 quoted both long-term changelogs as listing the same line. Only RouterOS 6.49.23 reads "system - improve stability (includes CVE-2026-84411);" (MikroTik forum, 2026-10-09). The RouterOS 7.23.8 changelog reads "system - improve stability (includes CVE-2026-84411, CVE-2026-103903);", so 7.23.8 also fixes a second flaw, CVE-2026-103903, that MikroTik's changelog names without describing (MikroTik, 2026-10-08). The upgrade advice is unchanged.

Builds on: CERT Polska confirms active exploitation of an unauthenticated SSH takeover chain against…

vulnerability10 Oct 03:50Zmulti-sourceOpen finding →

2026-09-06 · view entry permalink →

CRITICALCVE-2026-67276 +5exploitedupdatedNATOA1

CVE-2026-67279 / CVE-2026-86060, MikroTik RouterOS "MikroTrick": an SSH rekey-during- authentication state-confusion bypass chained with a crafted-username privilege escalation reaches unauthenticated full device takeover, actively exploited

CERT Polska (NASK) coordinated disclosure of six MikroTik RouterOS vulnerabilities on 2026-09-05, naming the combination that yields unauthenticated full device takeover "MikroTrick," and states plainly that it has independent confirmation of ongoing, successful attacks against RouterOS devices whose SSH service is reachable from the internet (CERT Polska, 2026-09-05). The exploited chain combines two flaws in RouterOS's SSH authentication path. CVE-2026-67279 (CVSS 6.9) is a protocol state-confusion defect: when a client initiates an SSH key re-exchange before completing user authentication, the RouterOS SSH server "unconditionally moved from the temporary rekey state to channel handling instead of resuming the interrupted authentication," accepting a session channel despite never sending SSH_MSG_USERAUTH_SUCCESS (CERT Polska, technical analysis, 2026-09-22). This does not by itself grant an authenticated identity or any privilege, but it is the precondition CVE-2026-86060 (CVSS 9.2, CWE-88 argument injection) then abuses: RouterOS's login helper accepts a username beginning with a hyphen as a command-line option rather than literal text, so a username of "-2" makes the helper read a replacement username and policy mask from file descriptor 2 (the same pseudoterminal the SSH channel already controls) letting the attacker supply their own privilege mask over the SSH channel itself and escalate to full administrative privilege (CERT Polska, technical analysis, 2026-09-22). No credential, no key, and no completed authentication stands between internet reach to the SSH port and full device compromise. A third, narrower flaw, CVE-2026-67276, was wrongly associated with this chain in some earlier reporting; CERT Polska's own technical write-up states it "is a separate vulnerability that allows an attacker to impersonate a user authenticated with an RSA key," requiring the target account name and RSA modulus in advance and granting access only to that one account; "significantly less suitable for a mass attack that works regardless of device configuration" (CERT Polska, technical analysis, 2026-09-22), and it is not confirmed separately exploited.

An independent researcher's reverse-engineering of the silent 2026-09-03 patch traces the mechanics of the crafted-username step in more detail: the SSH daemon invokes a legacy login helper via a system call, passing the authenticated username and a decimal policy-mask value as trailing positional arguments, and that helper's undocumented legacy transport treats any positional argument beginning with a hyphen as a file-descriptor number, reading up to 4096 bytes from it and splitting the result on null bytes into a replacement identity and a replacement policy mask (Nick Pratley, 2026-09-04). The researcher reproduced full policy-mask override once a username matching this pattern was accepted, but did not reproduce a stock, credential-free way to make SSH accept that username in the first place, leaving CERT Polska's combination of the two coordinated CVEs, rather than this third-party analysis, as the authoritative description of the unauthenticated attack path. CERT Polska's own investigation of the observed intrusions found the operators create a highly-privileged local account after exploitation, with the log sequence recording a failed login for a numeric pseudo-user immediately followed by that user's creation over the same SSH session, and states this activity has been occurring since at least 2026-09-02 (CERT Polska, 2026-09-05).

Three further CVEs round out the coordinated disclosure at lower severity, alongside CVE-2026-67276 above. CVE-2026-67277 (CVSS 8.8) lets an unauthenticated client reach the bandwidth-test service's post-authentication code path; combined with disclosure of uninitialized kernel packet-buffer contents and an integer-underflow size-validation bug, this yields kernel memory leakage or a remote denial-of-service that restarts the device (CERT Polska, CVE detail page, 2026-09-05); CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-10, confirming active in-the-wild exploitation (CISA KEV, catalogue version 2026.09.10). CVE-2026-67278 and CVE-2026-67281 are not confirmed separately exploited. CVE-2026-67278 (CVSS 6.3) lets an attacker who can intercept or redirect an outbound RouterOS TLS connection forge a trusted intermediate certificate for arbitrary hostnames, because RouterOS accepts malformed RSA/PKCS#1 v1.5 signatures during X.509 validation and its trust store ships a root CA with public exponent 3, enabling TLS server impersonation against the device's own outbound connections without the root's private key. CVE-2026-67281 (CVSS 8.7) is an unauthenticated file-read in the WebFig /jsproxy path: a newly allocated session retains a stale, uninitialized pointer used for file-authorization checks, and an attacker who can influence allocator state and supplies parent-directory traversal components in an encrypted URI can escape the WebFig file namespace and disclose root-owned files, including credential-bearing configuration stores.

Five of the six are fixed in RouterOS 7.25beta3, 7.24.2, 7.23.4 and 6.49.21, released 2026-09-03; CVE-2026-67278 is not, because those releases carried an incomplete fix for it and it is resolved only in 7.23.6 (long-term) and 7.24.3 (stable) (CERT Polska, CVE detail page). On the releases that do fix their five, MikroTik pushed a first-ever in-app push notification to administrators alongside the release (CERT Polska, 2026-09-05). The fixed releases add a startup "Flagged" self-check that scans configuration for known post-compromise traces, disables recognized suspicious entries, and logs a critical warning, but CERT Polska is explicit that this mechanism detects only selected traces left after a compromise, and its absence is not proof that a device is safe (CERT Polska, 2026-09-05).

CERT Polska states the six flaws were found using an agentic research environment built on OpenAI's GPT-5.5-cyber and GPT-5.6-sol models under the OpenAI Government and Trust Agency Collaboration program, automating protocol-state-machine modelling and binary-diff hypothesis generation inside an isolated RouterOS lab, with every hypothesis confirmed on real hardware before publication (CERT Polska, 2026-09-05), a national CERT's AI-augmented research pipeline producing an actively-exploited, pre-auth full-device-takeover chain.

Detection concept, telemetry class first: on-device system-log review is the primary hunt surface here, since these are commodity routers with no EDR agent. Alert on any SSH login-failure log entry for a non-standard, negative-looking numeric pseudo-username, especially one immediately followed within the same session window by a new-user-creation log entry, CERT Polska's own observed intrusions show exactly this sequence. Independently alert on creation of any locally-administered account with full or administrative group membership that does not correlate to a known change-management action. For the WebFig file-disclosure path, web-access logs showing /jsproxy requests carrying encoded parent-directory traversal sequences are the anchor; for the bandwidth-test flaw, unexpected inbound connections to that service from unauthenticated sources, or device reboots correlated with such connections, are the observable. Triage: a device's own "Flagged" status is a useful positive signal but never a negative one, treat it as one input alongside the log markers above, not as a clearance check, per the vendor and CERT Polska's shared caution.

MikroTik RouterOS contains a missing authentication for critical function vulnerability which allows kernel memory disclosure and denial of service in the btest service.

CISA KEV 2026-09-10

We have obtained confirmation that the attackers are exploiting this combination of vulnerabilities to take full control of devices whose SSH service is accessible from public networks. It has also been confirmed that the released patches prevent the observed attacks.

RouterOS did not properly verify public keys used for SSH authentication - in particular, it did not compare the entire RSA public key assigned to a user.

CERT Polska

Because signature verification uses the client-supplied key, an attacker knowing an authorized RSA modulus can supply a key with exponent one, forge a valid signature, and open an SSH command channel as the target user without the private key.

Exploitation requires an unauthenticated SSH session to reach the RouterOS login helper.

CERT Polska (NASK), per-CVE detail page 2026-09-05

the successful attacks observed so far, including the creation of the "ops" account

CERT Polska

This mechanism detects only selected traces left after a compromise - the absence of the marker is not proof that the device is safe.

CERT Polska (NASK) 2026-09-05
Updaterun 2026-09-11T0410Z-intelsummarycvessourcesevidencebody

CISA added CVE-2026-67277 (the bandwidth-test kernel-memory-disclosure and denial-of-service flaw among this disclosure's four lower-severity CVEs) to its Known Exploited Vulnerabilities catalog on 2026-09-10, describing it as a "missing authenticaion for critical function vulnerability which allows kernel memory disclosure and denial of service in the btest service" (CISA KEV, catalogue version 2026.09.10), a misspelling CISA has since corrected in the live catalogue. CERT Polska's own technical analysis states CVE-2026-86060 was added to KEV the same day alongside it (CERT Polska, technical analysis, 2026-09-22). CVE-2026-67277's KEV addition confirms active in-the-wild exploitation of a third vulnerability in the coordinated disclosure, beyond the two (CVE-2026-67279, CVE-2026-86060) CERT Polska had already reported exploited directly; the remaining three lower-severity CVEs (CVE-2026-67276, CVE-2026-67278, CVE-2026-67281) are still not confirmed separately exploited by any source. The remediation is unchanged, all six flaws share the same fixed releases (6.49.21, 7.23.4, 7.24.2, 7.25beta3) already covered by this entry's patch guidance. Separately, per-CVE affected-version ranges have been corrected: only CVE-2026-67277, CVE-2026-67279 and CVE-2026-86060 reach back to the 6.x branch (6.0.0 before 6.49.21); the narrower RSA-impersonation flaw, CVE-2026-67276, affects only 7.9 before 7.23.4 and 7.24 before 7.24.2, so a device on the 6.x branch is not exposed to that specific attack path (CERT Polska, CVE detail page, 2026-09-05); it remains reachable via CVE-2026-86060 and the other lower-severity flaws that do affect that branch, so the same patch guidance applies to all versions regardless.

Correctionrun 2026-09-23T0405Z-inteltitlesummarytagscvessourcesentitiesbody

CERT Polska's own technical analysis of MikroTrick (CERT Polska, 2026-09-22) states plainly that "some publications incorrectly associated CVE-2026-67276 with the MikroTrick chain"; it "is a separate vulnerability that allows an attacker to impersonate a user authenticated with an RSA key," requiring the target account name and RSA modulus in advance and granting access only to that one account, "significantly less suitable for a mass attack that works regardless of device configuration." This entry previously named CVE-2026-67276 as the chain's forged-signature entry point; that attribution is wrong, and CERT Polska does not confirm CVE-2026-67276 as separately exploited in the wild. The actual, configuration-independent entry point is CVE-2026-67279: "vulnerable versions of the RouterOS SSH server handled a rekey initiated during user authentication incorrectly. When the rekey finished, the server unconditionally moved from the temporary rekey state to channel handling instead of resuming the interrupted authentication" (CERT Polska, technical analysis, 2026-09-22), reaching a session channel despite never completing authentication, the precondition CVE-2026-86060's crafted "-2" username then abuses to set an attacker-controlled policy mask. The exploitation status is corrected accordingly: CVE-2026-67276 moves from exploited to patch-available and CVE-2026-67279 moves from patch-available to exploited, both now classed as auth-bypass. Separately, the fixed releases' Flagged self-check specifically watches at startup for an "ops" account newly created in the privileged "full" group, disabling it and logging a warning when found, a more precise trigger than this entry previously stated.

Correctionrun 2026-09-27T1308Z-auditcvesactionsbody

The remediation this entry gave for CVE-2026-67278 was wrong. RouterOS 7.23.4 and 7.24.2, the releases named here as fixing all six flaws of the coordinated disclosure, "included an incomplete fix" for this one, and CERT Polska's per-CVE page now lists it as affecting 7.0.0 below 7.23.6 and 7.24 below 7.24.3, fixed in 7.23.6 (long-term) and 7.24.3 (stable), crediting Robert Żegleń for reporting the gap (CERT Polska, CVE detail page). The other five CVEs in the disclosure, including the exploited SSH chain and the bandwidth-test flaw in CISA's catalogue, are unaffected by this correction and remain fixed in the originally-named releases. A device patched to 7.23.4 or 7.24.2 still accepts malformed RSA signatures during X.509 validation and SSH host-key authentication, so the update action now targets 7.23.6 and 7.24.3.

vulnerability06 Sep 04:35Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Deep dive1
  • Vulns1

Source distribution

  • cert.pl3 (25%)
  • cisa.gov2 (17%)
  • forum.mikrotik.com2 (17%)
  • mikrotik.com2 (17%)
  • bleepingcomputer.com1 (8%)
  • download.mikrotik.com1 (8%)
  • npratley.net1 (8%)
All cited sources (12)