{
  "id": "CVE-2026-16347",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-16347",
  "published_at": "2026-07-28T19:59:29.927Z",
  "title": "Improper restriction of excessive authentication attempts in MikroTik RouterOS and Cloud Hosted Router",
  "vendor": "MikroTik",
  "product": "RouterOS",
  "cvss": {
    "score": 8.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": {
    "category": "Router / network device",
    "confidence": "high",
    "reason": "known edge product: MikroTik RouterOS Improper restriction of excessive authentication"
  },
  "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.",
  "cwe": "CWE-307",
  "cvss_by_source": {
    "cna": 8.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "MikroTik",
        "product": "RouterOS",
        "ranges": [
          "All versions"
        ],
        "fixed_in": null
      },
      {
        "vendor": "MikroTik",
        "product": "Cloud Hosted Router",
        "ranges": [
          "All versions"
        ],
        "fixed_in": null
      }
    ],
    "workarounds": [
      "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.\n\n* Configure the unsuccessful-attempt time range (0.1 to 0.5 seconds) in /ip service for all services, including the API, once available.\n\n* Connect initially from a trusted network (LAN) port only, then configure the router per your security requirements.\n\n* Restrict/limit access to management services from untrusted networks.\n\n* Apply firewall rules to control and restrict access to management services where possible.\n\n* Use long, randomly generated passwords rather than weak or default-simple ones, to keep the brute-force search space impractically large.\n\n* Keep the default randomly generated device password, or replace it with an equally strong one, since minimum complexity isn't enforced by default.\n\n\n\nUsers are encouraged to reach out to MikroTik (https://mikrotik.com/support) for further support."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
