RouterOS 7.2
RouterOS 7.2
The RouterOS 7.2 reached end of service life on Jun 6, 2022 — RouterOS no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your RouterOS 7.2 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- routeros
- release
- 7.2
- product Label
- RouterOS
- release Label
- RouterOS 7.2
- codename
- lts
- latest Version
- 7.2.3
- release Date
- 2022-03-31
- maintained
- source Url
- https://endoflife.date/routeros
Lifecycle Dates
- End of Service Life
- Jun 6, 2022
- Last OEM Support
- Jun 6, 2022
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for RouterOS 7.2 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for RouterOS 7.2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for RouterOS 7.2 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
RouterOS 7.2 Support: Frequently Asked Questions
Is the RouterOS 7.2 still supported?
RouterOS ended support for the RouterOS 7.2 on Jun 6, 2022 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the RouterOS 7.2 end of service life (EOSL) date?
RouterOS lists the end of service life for the RouterOS 7.2 as Jun 6, 2022.
Can I keep using the RouterOS 7.2 after its EOSL date?
Yes. EOSL means RouterOS stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the RouterOS 7.2 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting RouterOS 7.2
7 published CVEs affect the RouterOS 7.2, including 3 rated critical or high severity. RouterOS no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2022-45313 | HIGH | 8.8 | Dec 5, 2022 | Mikrotik RouterOs before stable v7.5 was discovered to contain an out-of-bounds read in the hotspot process. This vulnerability allows attackers to execute arbitrary code via a crafted nova message. |
| CVE-2018-5951 | HIGH | 7.5 | Mar 2, 2020 | An issue was discovered in Mikrotik RouterOS. Crafting a packet that has a size of 1 byte and sending it to an IPv6 address of a RouterOS box with IP Protocol 97 will cause RouterOS to reboot imminently. All versions of RouterOS that supports EoIPv6 are vulnerable to this attack. |
| CVE-2025-6443 | HIGH | 7.2 | Jun 25, 2025 | Mikrotik RouterOS VXLAN Source IP Improper Access Control Vulnerability. This vulnerability allows remote attackers to bypass access restrictions on affected installations of Mikrotik RouterOS. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of remote IP addresses when processing VXLAN traffic. The issue results from the lack of validation of the remote IP address against configured values prior to allowing ingress traffic into the inte |
| CVE-2022-45315 | MEDIUM | 6.4 | Dec 5, 2022 | Mikrotik RouterOs before stable v7.6 was discovered to contain an out-of-bounds read in the snmp process. This vulnerability allows authenticated attackers to execute arbitrary code via a crafted packet. |
| CVE-2021-3014 | MEDIUM | 6.1 | Jan 4, 2021 | In MikroTik RouterOS through 2021-01-04, the hotspot login page is vulnerable to reflected XSS via the target parameter. |
| CVE-2024-54772 | MEDIUM | 5.4 | Feb 11, 2025 | An issue was discovered in the Winbox service of MikroTik RouterOS long-term release v6.43.13 through v6.49.13 and stable v6.43 through v7.17.2. A patch is available in the stable release v6.49.18. A discrepancy in response size between connection attempts made with a valid username and those with an invalid username allows attackers to enumerate for valid accounts. |
| CVE-2023-41570 | MEDIUM | 5.3 | Nov 14, 2023 | MikroTik RouterOS v7.1 to 7.11 was discovered to contain incorrect access control mechanisms in place for the Rest API. |