Description
MikroTik RouterOS contains a weakness in its API authentication handling that lacks effective safeguards against excessive login attempts. The system does not enforce meaningful rate-limiting, account lockout, or source-based restrictions, allowing repeated authentication failures to proceed without defensive response. In some versions, a fixed per-connection delay is present, but it can be bypassed through concurrent sessions, resulting in continued high-volume attempts. This deficiency increases the risk that an attacker could eventually obtain valid credentials and gain unauthorized access to administrative services.
Published: 2026-07-28
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability lies in MikroTik RouterOS and Cloud Hosted Router API authentication handling. Because the system does not enforce rate‑limiting, account lockout, or source‑based restrictions, an attacker can repeatedly submit login attempts without triggering any defensive response. This flaw allows a legitimate attacker to recover valid credentials through brute force, eventually gaining full administrative control over the device and the network configurations it manages. The weakness is a classic implementation of CWE‑307, which involves insecure authentication mechanisms.

Affected Systems

The affected entities are MikroTik RouterOS firmware and the MikroTik Cloud Hosted Router. Specific compatible versions are not listed in the data, so the flaw may be present in current releases and earlier ones. Administrators should treat all RouterOS and Cloud Hosted Router deployments as potentially exposed until they ascertain the exact version scope.

Risk and Exploitability

With a CVSS score of 8.7, the flaw is classified as high severity, indicating significant potential impact on confidentiality, integrity, and availability. The EPSS score of less than 1% reflects a low but non‑zero exploitation likelihood in the wild, and the vulnerability is currently not listed in the CISA KEV catalog. Attackers can reach the exposed API over public networks, as described in the CVE text; this inference about the attack surface is drawn directly from the vulnerability description, implying that the main vector is unauthenticated attempts to the API interface.

Generated by OpenCVE AI on August 3, 2026 at 14:25 UTC.

Remediation

Vendor Workaround

No fix is currently available from MikroTik. Until a fix is available, MikroTik recommends that users adopt the following mitigations: Use a strong VPN or other additional protection layer if the API is exposed to public networks. * Configure the unsuccessful-attempt time range (0.1 to 0.5 seconds) in /ip service for all services, including the API, once available. * Connect initially from a trusted network (LAN) port only, then configure the router per your security requirements. * Restrict/limit access to management services from untrusted networks. * Apply firewall rules to control and restrict access to management services where possible. * Use long, randomly generated passwords rather than weak or default-simple ones, to keep the brute-force search space impractically large. * Keep the default randomly generated device password, or replace it with an equally strong one, since minimum complexity isn't enforced by default. Users are encouraged to reach out to MikroTik (https://mikrotik.com/support) for further support.


OpenCVE Recommended Actions

  • Configure the "unsuccessful‑attempt" time range setting in /ip service for all services, including the API, once the option becomes available in the firmware release
  • Apply firewall rules to limit or block management API access from untrusted networks and allow it only from trusted LAN interfaces
  • Use a strong VPN or other secure tunnel for all API traffic when the device is connected to external networks
  • Set long, randomly generated passwords for all local accounts and retain or replace the default device password with a strong one
  • Restrict or limit access to management services from untrusted networks using network segmentation and firewall policies
  • Monitor for firmware updates from MikroTik and apply any security patches as soon as they are released

Generated by OpenCVE AI on August 3, 2026 at 14:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 29 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
First Time appeared Mikrotik
Mikrotik cloud Hosted Router
Mikrotik routeros
Vendors & Products Mikrotik
Mikrotik cloud Hosted Router
Mikrotik routeros

Wed, 29 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 28 Jul 2026 20:00:00 +0000

Type Values Removed Values Added
Description MikroTik RouterOS contains a weakness in its API authentication handling that lacks effective safeguards against excessive login attempts. The system does not enforce meaningful rate-limiting, account lockout, or source-based restrictions, allowing repeated authentication failures to proceed without defensive response. In some versions, a fixed per-connection delay is present, but it can be bypassed through concurrent sessions, resulting in continued high-volume attempts. This deficiency increases the risk that an attacker could eventually obtain valid credentials and gain unauthorized access to administrative services.
Title Improper restriction of excessive authentication attempts in MikroTik RouterOS and Cloud Hosted Router
Weaknesses CWE-307
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Mikrotik Cloud Hosted Router Routeros
cve-icon MITRE

Status: PUBLISHED

Assigner: icscert

Published:

Updated: 2026-07-29T13:57:56.713Z

Reserved: 2026-07-20T20:41:22.596Z

Link: CVE-2026-16347

cve-icon Vulnrichment

Updated: 2026-07-29T13:57:41.343Z

cve-icon NVD

Status : Deferred

Published: 2026-07-28T20:17:23.713

Modified: 2026-07-30T14:12:18.697

Link: CVE-2026-16347

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T14:30:18Z

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts