BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-67276High confidence

SSH user impersonation possible in Mikrotik RouterOS

Mikrotik · RouterOS

9.2CriticalCVSS 4.0
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 6.45% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Mikrotik RouterOS and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-72024

EU known exploited

RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. 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.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

EUVD state
Present in the current official mapping
Known exploitation
Recorded by ENISA since 5 Sep 2026. Evidence sources: eukev_kev.
ENISA score
9.2 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. 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.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

What

RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. 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.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. 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.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Verification of Cryptographic Signature → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-347 ↗

CWE-347: Improper Verification of Cryptographic Signature. The product does not verify, or incorrectly verifies, the cryptographic signature for data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-347Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-72024Known-exploited evidence recorded

RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. 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.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

Official EUVD record ↗
BSI · German · WID-SEC-2026-3193MikroTik RouterOS: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in MikroTik RouterOS ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um einen Denial of Service Zustand herbeizuführen und um die Kontrolle über betroffene Geräte zu übernehmen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AL26-20AL26-020 - Vulnerabilities Impacting MikroTik RouterOS - CVE-2026-67276, CVE-2026-67277 and CVE-2026-86060

An Alert is used to raise awareness of a recently identified cyber threat that may impact cyber information assets, and to provide additional detection and mitigation advice to recipients. The Canadian Centre for Cyber Security ("Cyber Centre") is also available to provide additional assistance regarding the content of this Alert to recipients as requested.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-887Mikrotik security advisory (AV26-887) – Update 2

As of September 3, 2026, Mikrotik is affected by vulnerabilities in the following product: Open-source reporting indicates that CVE-2026-67276, CVE-2026-67277 and CVE-2026-86060 related to MikroTik are being exploited in the wild.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260909Security Bulletin 9 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 9 Sep 2026, published on 9 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
INCIBE-CERT · Spanish · multiples-vulnerabilidades-en-routeros-de-mikrotikMúltiples vulnerabilidades en RouterOS de MikroTik

El equipo CERT Polska ha publicado 3 vulnerabilidades: 2 de severidad crítica y 1 de severidad alta que en caso de ser explotadas, podrían permitir a un atacante crear una clave diferente e iniciar sesión mediante SSH, elevar sus privilegios, una fuga de memoria del kernel o un ataque DoS remoto.

Official advisory ↗
INCIBE-CERT · Spanish · actualizacion-11092026-multiples-vulnerabilidades-en-routeros-de-mikrotik[Actualización 11/09/2026] Múltiples vulnerabilidades en RouterOS de MikroTik

El equipo CERT Polska ha publicado 3 vulnerabilidades: 2 de severidad crítica y 1 de severidad alta que en caso de ser explotadas, podrían permitir a un atacante crear una clave diferente e iniciar sesión mediante SSH, elevar sus privilegios, una fuga de memoria del kernel o un ataque DoS remoto.

Official advisory ↗
CSIRT Italia · Italian · mikrotik-rilevato-sfruttamento-in-rete-di-nuove-vulnerabilitaMikroTik: rilevato sfruttamento in rete di nuove vulnerabilità

Rilevato lo sfruttamento attivo in rete delle vulnerabilità CVE-2026-67276 e CVE-2026-86060 – già sanate dal vendor – presenti nei prodotti Mikrotik RouterOS. Di seguito sono riportati i dettagli: CVE-2026-67276 : la vulnerabilità, di tipo " Improper verification " e con score CVSS v4.0 pari a 9.2, è dovuta a meccanismi di validazione non adeguati relativi alle chiavi pubbliche RSA durante il processo di autenticazione SSH. Un utente malintenzionato remoto, qualora sia a conoscenza del nome utente e parte delle informazioni associate alla chiave pubblica dell'account target, potrebbe eludere i meccanismi di autenticazione e ottenere un accesso non autorizzato ai sistemi interessati con i privilegi dell'utente impersonato. CVE-2026-86060 : la vulnerabilità, di tipo " Argument injection " e con score CVSS v4.0 pari a 9.2, è dovuta a meccanismi di controllo non adeguati dei nomi utente durante il processo di autenticazione SSH. In particolare, il sistema non gestisce adeguatamente nomi utente che iniziano con caratteri non consentiti, permettendo la manipolazione delle policy associate alla sessione di autenticazione. Un utente malintenzionato remoto, mediante l'utilizzo di un nome utente opportunamente predisposto, potrebbe elevare i propri privilegi sui sistemi interessati.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-035745MikroTikのrouterosにおけるデジタル署名の検証に関する脆弱性

RouterOSは、SSH認証要求を認可されたユーザーキーと照合する際に、RSA公開鍵全体を比較せず、キータイプと法（モジュラス）のみを確認し、指数は省略しています。署名検証にはクライアントが提供したキーを使用するため、攻撃者が認可されたRSAの法を知っている場合、指数を1に設定したキーを提供して有効な署名を偽造し、秘密鍵なしでターゲットユーザーとしてSSHコマンドチャネルを開くことが可能です。この問題は7.xブランチのみに影響し、以下のバージョンで修正されました：7.23.4（長期サポート版）および7.24.2（安定版）です。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0345Kwetsbaarheden verholpen in MikroTik RouterOS

RouterOS 7.x contained a critical SSH authentication vulnerability where only the RSA key type and modulus were verified, ignoring the exponent, enabling signature forgery and unauthorized access, fixed in versions 7.23.4 and 7.24.2.

Official advisory ↗
CERT Polska · Polish · mikrotrick-analiza-technicznaCERT Polska w social mediach

Opisujemy techniczne szczegóły łańcucha MikroTrick, złożonego z podatności CVE-2026-67279 i CVE-2026-86060, które w połączeniu pozwalały przejąć pełną kontrolę nad urządzeniem bez uwierzytelnienia. Wyjaśniamy mechanizm obserwowanych w internecie ataków, przebieg skoordynowanego ujawnienia obu podatności oraz praktyczną rolę agentów LLM w badaniach RouterOS.

Official advisory ↗
CERT Polska · Polish · mikrotik-routeros-cveCERT Polska w social mediach

Podczas badań własnych Sławomir Rozbicki z zespołu CERT Polska odkrył podatności w oprogramowaniu MikroTik RouterOS i wraz z pozostałymi członkami zespołu uczestniczył w koordynacji ich ujawnienia. Szczegóły dotyczące tego, w jaki sposób odkryto te podatności, wraz z innymi powiązanymi informacjami, są dostępne w naszym osobnym artykule . Podatność CVE-2026-67276 : RouterOS nie porównuje kompletnego klucza publicznego RSA podczas dopasowywania żądania uwierzytelnienia SSH do klucza autoryzowanego użytkownika, sprawdzając typ klucza i moduł, ale pomijając wykładnik. Ponieważ weryfikacja podpisu wykorzystuje klucz dostarczony przez klienta, atakujący znający autoryzowany moduł RSA może dostarczyć klucz z wykładnikiem równym jeden, sfałszować prawidłowy podpis i otworzyć kanał poleceń SSH jako docelowy użytkownik bez klucza prywatnego. Podatność CVE-2026-67277 : RouterOS akceptuje połączenie btest typu "related" przed zakończeniem uwierzytelniania odpowiadającej mu głównej sesji. Nieuwierzytelniony klient może wykorzystać ten stan do uruchomienia testu IPv4 UDP. Przy ustawieniu "random-data=false" nadawca transmituje niezainicjowany fragment końcowy z bufora pakietów jądra. Osobny, niesprawdzany i odwrócony przedział rozmiaru pakietu powoduje błąd typu integer underflow, co umożliwiało wyciek pamięci jądra albo zdalny atak DoS prowadzący do restartu systemu. Podatność CVE-2026-67279 : RouterOS SSH przechodzi do protokołu połączenia po zażądanej przez klienta renegocjacji kluczy, mimo że nie podjęto próby uwierzytelnienia użytkownika, co umożliwia nieuwierzytelnionemu klientowi otwarcie kanału sesji i wysłanie żądania exec. W podatnych wersjach serwer wykonuje polecenie, umożliwiając nieuwierzytelnione utworzenie, nadpisanie i odtworzenie plików w przestrzeni nazw plików zarządzanej przez RouterOS, w tym plików pomocniczych zawierających dane konfiguracyjne i diagnostyczne. Podatność CVE-2026-67281 : RouterOS WebFig zawiera podatność umożliwiającą nieuwierzytelniony odczyt plików poprzez ścieżkę /jsproxy , w której nowo utworzona sesja zachowuje nieaktualny, niezainicjalizowany wskaźnik do danych określających uprawnienia, wykorzystywany podczas autoryzacji dostępu do plików. Nieuwierzytelniony atakujący może odpowiednio przygotować stan alokatora pamięci, aby mechanizm udostępniania plików wykorzystał ten wskaźnik z wystarczającymi uprawnieniami, a następnie użyć komponentów wskazujących na katalog nadrzędny w zaszyfrowanym URI w celu opuszczenia przestrzeni plików WebFig i ujawnienia plików należących do użytkownika root, w tym plików konfiguracyjnych zawierających dane uwierzytelniające. Podatność CVE-2026-86060 : RouterOS zawiera błąd w obsłudze argumentów w ścieżce logowania SSH, dotyczący nazw użytkowników zaczynających się od zabronionego znaku. Pozwala to na zmianę zaufanej maski polityk RouterOS, co prowadzi do eskalacji uprawnień. Wykorzystanie tej luki wymaga nieautoryzowanej sesji SSH. Problemy te zostały naprawione w wersjach: 6.49.21 (Long-term), 7.23.4 (Long-term) i 7.24.2 (Stable). Podatność CVE-2026-67278 : MikroTik RouterOS akceptuje nieprawidłowe podpisy RSA/PKCS#1 v1.5 w usługach opartych na RSA, w tym podczas walidacji certyfikatów TLS/X.509 oraz uwierzytelniania klucza hosta SSH. Ponieważ magazyn zaufanych certyfikatów (trust store) zawiera główny certyfikat CA z wykładnikiem e=3, atakujący kontrolujący lub przekierowujący wychodzące połączenie TLS z RouterOS może wykorzystać publiczny certyfikat głównego CA – bez posiadania jego klucza prywatnego – do sfałszowania zaufanego certyfikatu pośredniego i wystawienia certyfikatów dla dowolnych nazw hostów, co umożliwia podszycie się pod serwer TLS. Ten sam problem wpływa również na uwierzytelnianie SSH oparte na RSA. Problem dotyczy wyłącznie gałęzi 7.x i został naprawiony w wersjach: 7.23.6 (Long-term) oraz 7.24.3 (Stable). Wersje 7.23.4 oraz 7.24.2 zawierały niepełną poprawkę. Dziękujemy Robertowi Żegleniowi za zgłoszenie tego problemu. Więcej o procesie zgłaszania podatności można przeczytać na stronie https://cert.pl/cvd/ . CERT Polska to zespół działający w strukturach NASK - Państwowego Instytutu Badawczego, powołany w 1996 roku do reagowania na incydenty bezpieczeństwa komputerowego. Realizuje zadania CSIRT NASK, jednego z trzech takich zespołów działających na poziomie krajowym w ramach krajowego systemu cyberbezpieczeństwa. CERT Polska w social mediach Facebook X LinkedIn GitHub Kontakt ul. Kolska 12, 01-045 Warszawa ePUAP: /NASK-Instytut/SkrytkaESP e-Doręczenia: AE:PL-60057-61611-BCEGR-11 e-mail: [email protected] Zgłaszanie incydentów: incydent.cert.pl [email protected] © 2026 NASK Polityka prywatności Deklaracja dostępności CSIRT GOV CSIRT MON

Official advisory ↗
CERT Polska · Polish · podatnosci-w-mikrotik-routeros-aktywnie-wykorzystywaneCERT Polska w social mediach

Zespół CERT Polska zidentyfikował i skoordynował ujawnienie sześciu podatności w MikroTik RouterOS, w tym dwóch krytycznych. Podatności te są już aktywnie wykorzystywane do przejmowania urządzeń, których usługa SSH jest dostępna z internetu. Zalecamy pilną aktualizację urządzeń do poprawionych wersji oraz weryfikację konfiguracji pod kątem śladów kompromitacji.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4
Fixed
The Cyber Centre recommends that organizations using MikroTik RouterOS, review the MikroTik security bulletin Footnote 1 and update/upgrade the affected devices to the following vendor-supported fixed versions: Affected product Affected versions Fixed versions RouterOS 6.x Versions prior to 6.49.21 Version 6.49.21 RouterOS 7.x Long-Term Versions prior to 7.23.4 Version 7.23.4 RouterOS 7.x Stable Versions prior to 7.24.2 Version 7.24.2 RouterOS Development Branch Versions prior to 7.25 beta 3 Version 7.25 beta 3 The Cyber Centre recommends following guidance provided by MikroTik Footnote 1 and CERT Polska Footnote 11 to immediately update RouterOS, along with checking logs for possible device compromise. If the logs have a critical entry saying device has been “Flagged”, MikroTik recommends following the instructions provided by the status site Footnote 12 . The Cyber Centre also recommends organizations to: Determine the current version of software on each appliance. Prioritize patching for systems exposing SSH to the internet. Monitor authentication logs and network activity for indications of unauthorized access. After patching, verify that the appliance is running the updated version and review logs for unusual activity. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre’s Top 10 IT Security Actions Footnote 13 with an emphasis on the following topics: Consolidate, monitor, and defend Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal or email contact@cyber.gc.ca .
Action
Apply the fixed release for the affected product branch as recorded by Canadian Centre for Cyber Security. Validate the exact product and build in the linked advisory before deployment.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 5 Sept 2026 · Last source change 9 Sept 2026, 04:26 UTC · CWE-347 · Improper Verification of Cryptographic Signature

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-06
European sourceENISA EUVD · EUVD-2026-72024
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4 · Fixed: The Cyber Centre recommends that organizations using MikroTik RouterOS, review the MikroTik security bulletin Footnote 1 and update/upgrade the affected devices to the following vendor-supported fixed versions: Affected product Affected versions Fixed versions RouterOS 6.x Versions prior to 6.49.21 Version 6.49.21 RouterOS 7.x Long-Term Versions prior to 7.23.4 Version 7.23.4 RouterOS 7.x Stable Versions prior to 7.24.2 Version 7.24.2 RouterOS Development Branch Versions prior to 7.25 beta 3 Version 7.25 beta 3 The Cyber Centre recommends following guidance provided by MikroTik Footnote 1 and CERT Polska Footnote 11 to immediately update RouterOS, along with checking logs for possible device compromise. If the logs have a critical entry saying device has been “Flagged”, MikroTik recommends following the instructions provided by the status site Footnote 12 . The Cyber Centre also recommends organizations to: Determine the current version of software on each appliance. Prioritize patching for systems exposing SSH to the internet. Monitor authentication logs and network activity for indications of unauthorized access. After patching, verify that the appliance is running the updated version and review logs for unusual activity. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre’s Top 10 IT Security Actions Footnote 13 with an emphasis on the following topics: Consolidate, monitor, and defend Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal or email contact@cyber.gc.ca .
    Canadian Centre for Cyber Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Canadian Centre for Cyber Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    7.24 < 7.24.2; 7.9 < 7.23.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    7.24 < 7.24.2; 7.9 < 7.23.4 · Fixed: The Cyber Centre recommends that organizations using MikroTik RouterOS, review the MikroTik security bulletin Footnote 1 and update/upgrade the affected devices to the following vendor-supported fixed versions: Affected product Affected versions Fixed versions RouterOS 6.x Versions prior to 6.49.21 Version 6.49.21 RouterOS 7.x Long-Term Versions prior to 7.23.4 Version 7.23.4 RouterOS 7.x Stable Versions prior to 7.24.2 Version 7.24.2 RouterOS Development Branch Versions prior to 7.25 beta 3 Version 7.25 beta 3 The Cyber Centre recommends following guidance provided by MikroTik Footnote 1 and CERT Polska Footnote 11 to immediately update RouterOS, along with checking logs for possible device compromise. If the logs have a critical entry saying device has been “Flagged”, MikroTik recommends following the instructions provided by the status site Footnote 12 . The Cyber Centre also recommends organizations to: Determine the current version of software on each appliance. Prioritize patching for systems exposing SSH to the internet. Monitor authentication logs and network activity for indications of unauthorized access. After patching, verify that the appliance is running the updated version and review logs for unusual activity. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre’s Top 10 IT Security Actions Footnote 13 with an emphasis on the following topics: Consolidate, monitor, and defend Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal or email contact@cyber.gc.ca .
    Canadian Centre for Cyber Security ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Canadian Centre for Cyber Security ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: added remediation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited; removed remediation: cyber.gc.ca/al26-020-vulnerabilities-impacting-mikrotik-routeros-cve-2026-67276-cve-2026-67277-cve-2026-86060.
    Before
    mitigation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited · remediation: cyber.gc.ca/al26-020-vulnerabilities-impacting-mikrotik-routeros-cve-2026-67276-cve-2026-67277-cve-2026-86060 · vendor advisory: mikrotik.com/september-2026-vulnerability
    After
    mitigation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited · remediation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited · vendor advisory: mikrotik.com/september-2026-vulnerability
    cvd@cert.pl ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4 · Fixed: The Cyber Centre recommends that organizations using MikroTik RouterOS, review the MikroTik security bulletin Footnote 1 and update/upgrade the affected devices to the following vendor-supported fixed versions: Affected product Affected versions Fixed versions RouterOS 6.x Versions prior to 6.49.21 Version 6.49.21 RouterOS 7.x Long-Term Versions prior to 7.23.4 Version 7.23.4 RouterOS 7.x Stable Versions prior to 7.24.2 Version 7.24.2 RouterOS Development Branch Versions prior to 7.25 beta 3 Version 7.25 beta 3 The Cyber Centre recommends following guidance provided by MikroTik Footnote 1 and CERT Polska Footnote 11 to immediately update RouterOS, along with checking logs for possible device compromise. If the logs have a critical entry saying device has been “Flagged”, MikroTik recommends following the instructions provided by the status site Footnote 12 . The Cyber Centre also recommends organizations to: Determine the current version of software on each appliance. Prioritize patching for systems exposing SSH to the internet. Monitor authentication logs and network activity for indications of unauthorized access. After patching, verify that the appliance is running the updated version and review logs for unusual activity. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre’s Top 10 IT Security Actions Footnote 13 with an emphasis on the following topics: Consolidate, monitor, and defend Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal or email contact@cyber.gc.ca .
    After
    RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  7. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited; added remediation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited; removed remediation: cyber.gc.ca/al26-020-vulnerabilities-impacting-mikrotik-routeros-cve-2026-67276-cve-2026-67277-cve-2026-86060; 1 further additions.
    Before
    remediation: cyber.gc.ca/al26-020-vulnerabilities-impacting-mikrotik-routeros-cve-2026-67276-cve-2026-67277-cve-2026-86060
    After
    mitigation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited · remediation: cert.pl/vulnerabilities-in-mikrotik-routeros-actively-exploited · vendor advisory: mikrotik.com/september-2026-vulnerability
    cvd@cert.pl ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    7.24 < 7.24.2; 7.9 < 7.23.4 · Fixed: The Cyber Centre recommends that organizations using MikroTik RouterOS, review the MikroTik security bulletin Footnote 1 and update/upgrade the affected devices to the following vendor-supported fixed versions: Affected product Affected versions Fixed versions RouterOS 6.x Versions prior to 6.49.21 Version 6.49.21 RouterOS 7.x Long-Term Versions prior to 7.23.4 Version 7.23.4 RouterOS 7.x Stable Versions prior to 7.24.2 Version 7.24.2 RouterOS Development Branch Versions prior to 7.25 beta 3 Version 7.25 beta 3 The Cyber Centre recommends following guidance provided by MikroTik Footnote 1 and CERT Polska Footnote 11 to immediately update RouterOS, along with checking logs for possible device compromise. If the logs have a critical entry saying device has been “Flagged”, MikroTik recommends following the instructions provided by the status site Footnote 12 . The Cyber Centre also recommends organizations to: Determine the current version of software on each appliance. Prioritize patching for systems exposing SSH to the internet. Monitor authentication logs and network activity for indications of unauthorized access. After patching, verify that the appliance is running the updated version and review logs for unusual activity. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre’s Top 10 IT Security Actions Footnote 13 with an emphasis on the following topics: Consolidate, monitor, and defend Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal or email contact@cyber.gc.ca .
    After
    RouterOS: 7.24 < 7.24.2, 7.9 < 7.23.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  9. Remediation statusRemediation status changed from Patch available to Mitigation available.
    Before
    Patch available
    After
    Mitigation available
    cvd@cert.pl ↗
  10. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    cvd@cert.pl ↗
  11. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  12. Affected versionsThe structured affected or fixed version information changed.
    Before
    7.24 < 7.24.2; 7.0.0 < 7.23.4; 6.0.0 < 6.49.21 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    7.24 < 7.24.2; 7.9 < 7.23.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  13. ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.
    Before
    not listed in ENISA EUVD known-exploited dataset
    After
    listed in ENISA EUVD known-exploited dataset (EUVD-2026-72024)
    ENISA EUVD ↗
  14. ENISA EUVD mappingEUVD-2026-72024 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-72024"}
    ENISA EUVD ↗
  15. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-72024↗Canadian Centre for Cyber Security remediation guidance↗Mitigation reference↗Vendor advisory↗CVE authority or vendor reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-67276 · cve.blacktree.nl