RouterOS
| RouterOS | |
|---|---|
Winbox and RouterOS shell | |
| Developer | MikroTik |
| Release | 1997 |
| Stable release | 7.24.1
/ August 21, 2026 |
| Operating system | Linux |
| Platform | ARM, AArch64, x86, x86_64, PowerPC, SMIPS, MMIPS, MIPSBE |
| Included with | RouterBoard |
| Available in | English |
| License | GNU General Public License version 2 |
| Website | https://mikrotik.com/download |
RouterOS is a network operating system based on the Linux kernel developed by MikroTik, pre-installed on RouterBOARD devices.[1] It can also be installed on a PC, turning it into a router with a firewall, VPN server and client, and wireless access point. The system can serve as a customizable captive portal for a wireless access point. Additionally, MikroTik offers RouterOS images for use in virtual machines and cloud services, called Cloud Hosted Router (CHR), available as a virtual machine disk image for various virtualization solutions, including the Amazon Web Services marketplace.[2]
RouterOS can be configured via a command-line interface accessible through serial port, telnet, and Secure Shell (SSH), and via a graphical user interface available as a web-based interface (WebFig), a Microsoft Windows-based software application (Winbox), and apps for iOS and Android. An application programming interface (API) allows the development of specialized applications for monitoring and management.
SwOS is an operating system designed for RouterBOARD's line of switches. It is based on a subset of RouterOS features.
History
[edit]MikroTik was established in 1996 by founders John Tully and Arnis Riekstiņš in Riga, Latvia, developing networking software for x86 PC hardware that would develop into a product called RouterOS. The earliest versions of RouterOS were based on Linux 2.2.
In 2002, MikroTik expanded its product line by producing their own networking-focused low-power single-board computers (SBC), branded RouterBoard, that ran RouterOS. These early SBCs could be expanded and/or integrated as components of other systems, but as time passed, this RouterBoard/RouterOS platform would develop into a full line of network equipment.[3][additional citation(s) needed]
Licensing model
[edit]RouterOS is distributed free of charge. However, features are implemented using a tiered, pay-per-use licensing model.[4] Each RouterBOARD device comes with RouterOS and a specific license pre-installed, depending on its purpose; for installation on third-party devices, the customer must pay the license fee.
Standard
[edit]- 0 (24-hour trial): All features enabled for testing within a 24-hour period. Before the trial expires, the user must install a valid license.
- 1 (Free demo): Most features enabled (except routing protocols and wireless networks), limited to one instance for some of these. Requires a license key (free of charge).
- 3 (WISP CPE): Present in RouterBOARD CPE devices (wireless client and point-to-point/multipoint links). It is not commercially available as a separate product, and the license lacks features for wireless access points.
- 4 y 5 (WISP): All features enabled, with limits of 200 and 500 instances respectively for some of them. Available on low to mid-range RouterBOARD devices. he license key has a retail price of US$45 and US$95 respectively.
- 6 (Controller): All features enabled, without limitations. Available on high-end RouterBOARD devices. The license key has a retail price of for US$250.
Cloud Hosted Router
[edit]The licensing model for RouterOS in the cloud is as follows:[4]
- free: limited to 1 Mb/s per interface. No license key required.
- 60-day trial with no limitations. Requires a license key (free of charge).
- p1: perpetual license, limited to 1 Gb/s upload speed per interface. The license key has a retail price of US$45.
- p10: perpetual license, limited to 10 GB/s upload speed per interface. The license key has a retail price of US$95.
- p-unlimited: perpetual license, with no bandwidth limitations. The license key has a retail price of US$250.
RouterOS' cloud licensing model delivers all offered features without limitations, and is limited to one VM instance per license.
Versions
[edit]- RouterOS v7: December 6, 2021 (based on the Linux kernel version 5.6). The latest stable version is 7.24, released on August 14, 2026.[5]
- RouterOS v6: May 2013 (based on the Linux kernel 3.3.5). The latest stable, long-term version is 6.49.20, released on July 3, 2016.[5]
- RouterOS v5: March 2011 (based on the Linux kernel 2.6.35). The latest stable version is 5.26, released on September 14, 2013.[5]
- RouterOS v4: October 2009 (based on the Linux kernel 2.6.26). The latest stable version is 4.17, released on March 2, 2011.[5]
- RouterOS v3: January 2008 (based on the Linux kernel 2.4.31). The latest stable version is 3.30.[5]
Vulnerabilities
[edit]- Buffer overflow in the SMB protocol (CVE-2018-7445): A critical vulnerability in the built-in SMB file-sharing service that allowed an unauthenticated remote attacker to execute arbitrary code through specially crafted NetBIOS requests.[6]
- Vulnerabilities in WinBox (CVE-2018-14847 and CVE-2024-54772): Historically, the WinBox port (the software for managing RouterOS) has been the target of significant vulnerabilities. The most notorious case allowed directory traversal attacks to read and write configuration files without authentication. Later versions have also exhibited user enumeration issues through differences in response time or packet size.[7][8]
- RADVD Out-Of-Bounds Write (CVE-2023-32154): A critical vulnerability in the IPv6 Router Advertisement Daemon that allowed attackers adjacent to the network to execute arbitrary code with root privileges without prior authentication, due to poor data validation.[9]
- Memory corruption in SMB (CVE-2024-54952): A memory corruption vulnerability in the SMB service that allowed unauthenticated remote attackers to cause a denial-of-service attack by sending manipulated packets to block the file-sharing component.[10]
- Validación de VXLAN (CVE-2025-6443): Un fallo de control de acceso en el manejo de paquetes VXLAN donde el enrutador omitía la validación adecuada de las direcciones IP de origen remotas, permitiendo a atacantes eludir restricciones perimetrales.[11]
- Cross-site scripting in Hotspot (CVE-2025-6563): XSS vulnerability in captive portal functionality that allowed malicious code to be injected through the URL redirection parameter to compromise authenticated user sessions.[12]
- Buffer overflow in the REST API (CVE-2025-10948): Localized critical buffer overflow in the JSON parsing function through the REST API endpoint, allowing remote code execution.[13]
- WebFig exposure (CVE-2025-61481): Exposure of the default plain text (HTTP) web administration interface in certain initial configurations, facilitating on-path man-in-the-middle attacks to intercept credentials.[14]
- Out-of-bounds read in SCEP (CVE-2026-7668): Vulnerability in the SCEP certificate management library within the RouterOS version 6.49.x branches, exploitable by manipulating fields in certificate transactions.[15]
- Weaknesses in API session management (CVE-2026-14227): Failures in the expiration of active API sessions, allowing existing sessions to retain elevated privileges after changes in user permissions or group.[16]
- API Rate-Limiting Deficiency (CVE-2026-16347): Deficiencies in the handling of rate-limiting for authentication attempts in the operating system API.[17]
- Vulnerabilities to denial-of-service attacks (CVE-2026-39042): Logical flaws in internal libraries (such as in the processing of analysis functions) that could cause unexpected restarts or system crashes in response to malformed packets.[18]
References
[edit]- ↑ "MikroTik – What is it, who is it for, and when is it worth it? RouterOS v7, devices, costs, and security". Retrieved 2026-08-26.
- ↑ "What is the MikroTik RouterOS? Features & Capabilities". www.netmaker.io. Retrieved 2026-08-22.
- ↑ "MikroTik - About us". MikroTik.
- 1 2 "Manual:License - MikroTik Wiki". wiki.mikrotik.com. Retrieved August 7, 2020.
{{cite web}}: CS1 maint: url-status (link) - 1 2 3 4 5 "MikroTik". mikrotik.com. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2018-7445". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2018-14847". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2024-54772". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2023-32154". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2024-54952". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2025-6443". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2025-6563". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2025-10948". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2025-61481". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2026-7668". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2026-14227". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2026-16347". nvd.nist.gov. Retrieved 2026-08-22.
- ↑ "NVD - CVE-2026-39042". nvd.nist.gov. Retrieved 2026-08-22.