MikroTik RouterOS Vulnerabilities & Security Advisories
19 advisories tracked · MikroTik Security Announcements + NVD · 3 listed in the CISA Known Exploited Vulnerabilities catalog
Every row below is a published MikroTik advisory that VulniPulse classified as RouterOS, with the CVEs, affected and fixed releases and exploitation status the vendor stated. Severity mix: 3 critical, 8 high, 7 medium.
Android app · Google Play
Monitor MikroTik CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Source
MikroTik Security Announcements + NVD
MikroTik publishes official security announcements at mikrotik.com/supportsec, but has no machine-readable feed and its CVEs are assigned by several CNAs. VulniPulse joins NVD candidate metadata to the server-rendered official announcement index, then releases an alert only after fetching the linked article and verifying its CVE identity in the article heading or body. Covers RouterOS (v6/v7), SwOS, Winbox, The Dude and MikroTik router/switch hardware (hEX, CCR, CRS, cAP, wAP).
Latest MikroTik RouterOS advisories
Medium [CVE-2026-89021] MikroTik RouterOS before 7.24.2 contains a path traversal vulnerability in the container package OCI/tar image extraction that allows attackers to write files outside the container root by supplying a crafted container image with symlinks pointing to arbitrary paths
A path traversal vulnerability has been identified in the RouterOS container feature. When importing a container image, specially crafted links inside the image could cause files to be written or deleted outside of the container’s own directory, anywhere on the router’s storage. The container does not need to be started for this to happen, importing the image is enough. The issue has been assigned CVE-2026-89021. Who is affected: Only devices that use the container feature. The container package is not installed by default, and the feature has to be explicitly enabled by the administrator. If you do not use containers, you are not affected. RouterOS 6 does not have the container feature and is not affected. Who can trigger it: A user with the rights to add containers on the router. The risk comes from container images obtained from untrusted sources, so this is especially relevant if you pull images from public registries. This issue is fixed in RouterOS 7.24.2 (stable) and later releases. Note for long-term users: this fix is not included in the 7.23.x long-term branch and there is no backport planned. Affected product named by the advisory: MikroTik RouterOS.
Medium [CVE-2026-89020] MikroTik RouterOS before 7.23.4 (long-term) and 7.24.2 (stable) contains a stack-based buffer overflow vulnerability in the mtget binary's TFTP RRQ builder function that allows authenticated users to crash the mtget worker process by supplying a URL path of 507 bytes or more to the /tool fetch command; the first write outside the 528-byte buffer occurs at 505 bytes
A buffer overflow vulnerability has been identified in the “fetch” tool of RouterOS (/tool fetch), when it is given a very long tftp:// address. A logged-in user can use this to crash the fetch process. The issue has been assigned CVE-2026-89020. Who is affected: RouterOS versions 6 and 7 before the fixed releases listed below. To trigger the issue, the attacker needs a valid username and password on the router. Even a read-only user can trigger it, so this matters for devices with multiple user accounts or shared logins. Although the public report describes a crash, we treat this issue seriously, because memory corruption issues of this type can sometimes be abused for more than a crash. We recommend upgrading rather than relying on the limited user rights of your accounts. This issue is fixed in: 7.24.2 (stable). 7.23.4 (long-term). Users are advised to upgrade to one of these versions or any later release. Until you upgrade, review the user accounts on your router, remove accounts that are no longer needed, and make sure management services are not reachable from untrusted networks. Affected product named by the advisory: MikroTik RouterOS.
Medium [CVE-2026-67279] SSH Pre-Authentication Rekey State Bypass in MikroTik RouterOS
MikroTik has found a security vulnerability in RouterOS and releases containing a fix have been published in all channels. This is an important security update. Most configurations are not at risk, but upgrading is highly recommended. Update 2026-10-06: this article now lists all six issues from the original report, including a corrected fix version for one of them (see below). The CVE numbers were initially withheld to give users time to upgrade. Your device should already give you the option to upgrade software in the “Check for updates” menu. Fix is included in: 7.25 beta 3. 7.24.2. 7.23.4. 6.49.21. Important: the fix for one of the issues (CVE-2026-67278, forged certificates and SSH host keys) in 7.24.2 and 7.23.4 was found to be incomplete. The complete fix is included in 7.24.3 (stable) and 7.23.6 (long-term). If you already upgraded in September, please upgrade again to one of these versions or any later release. RouterOS 6 is not affected by this particular issue. For regular home device users the issue does not pose an immediate risk, but we still suggest all users to upgrade. Affected product named by the advisory: MikroTik RouterOS.
Medium [CVE-2026-67278] MikroTik RouterOS accepts malformed RSA/PKCS#1 v1.5 signatures across RSA-based services, including TLS/X.509 certificate validation and SSH host-key authentication
MikroTik RouterOS accepts malformed RSA/PKCS#1 v1.5 signatures across RSA-based services, including TLS/X.509 certificate validation and SSH host-key authentication. Because its trust store includes an e=3 root CA, an attacker controlling or redirecting an outbound RouterOS TLS connection can use the root’s public certificate - without its private key - to forge a trusted intermediate and issue certificates for arbitrary hostnames, enabling TLS server impersonation. The same permissive verification also undermines RSA-based SSH authentication. This issue affects only 7.x branch was fixed in versions: 7.23.6 (Long-term) and 7.24.3 (Stable). Releases 7.23.4 and 7.24.2 included an incomplete fix.
Medium [CVE-2023-47310] misconfiguration in the default settings of MikroTik RouterOS 7 allows incoming IPv6 UDP traceroute packets, which
A misconfiguration in the default settings of MikroTik RouterOS 7 allows incoming IPv6 UDP traceroute packets, which could permit unauthorized network reconnaissance from external sources. Users are advised to upgrade to RouterOS 6.49.13, 7.14, or any later version to address this vulnerability. MikroTik always recommends keeping RouterOS devices up to date and using a strong firewall to protect the device from traffic arriving from untrusted networks.
Medium [CVE-2024-54772] MikroTik RouterOS: Issue Summary A vulnerability has been identified in the WinBox service, where a discrepancy in response size between connection…
Issue Summary A vulnerability has been identified in the WinBox service, where a discrepancy in response size between connection attempts with valid and invalid usernames allows attackers to confirm if user accounts exists via brute forcing the login process. In other words, when attacker tries to log into the device, by examining the response, the attacker can deduce if such a user exists on the device. Even if username is found, password still needs to be guessed as well. Affected Versions RouterOS versions prior to 6.49.18 and 7.18. Recommended Actions Update RouterOS – Upgrade to 6.49.18, 7.18, or a newer version to patch the vulnerability. Monitor for unusual login attempts – Review router logs for suspicious authentication activity and take action accordingly. MikroTik always recommends keeping RouterOS devices up to date and using a strong firewall so WinBox and other management services are not reachable from untrusted networks. Mitigation strategies for devices that cannot be updated immediately Restrict WinBox Access. Firewall the WinBox port on public interfaces and untrusted networks. Affected products named by the advisory: MikroTik RouterOS.
Medium [CVE-2023-41570] RouterOS: MikroTik RouterOS v7.1 to 7.11 was discovered to contain incorrect access control mechanisms in place for the Rest API.
MikroTik RouterOS versions 7.1 through 7.11 contained an access control issue in the REST API. The issue applied to installations where the REST API was enabled and reachable, and could allow requests to be handled with incorrect access control. This issue is fixed in RouterOS 7.12 and newer releases. MikroTik always recommends keeping RouterOS devices up to date and using a strong firewall so API and management services are available only from trusted networks.