Critical

MikroTik RouterOS and Cloud Hosted Router

All CISA Advisories

Overview

MikroTik has disclosed a significant vulnerability affecting all versions of its RouterOS and Cloud Hosted Router software, identified as CVE-2026-16347. This flaw allows attackers to bypass safeguards against excessive login attempts, making it easier for them to guess passwords and gain unauthorized access to systems. Users worldwide are at risk, particularly in sectors like information technology and commercial facilities. Currently, no fix is available, prompting MikroTik to advise users to implement several mitigations, such as using strong VPNs, restricting access from untrusted networks, and employing long, complex passwords. The vulnerability underscores the need for organizations to bolster their security measures to protect against potential breaches.

Key Takeaways

  • Affected Systems: MikroTik RouterOS (all versions), MikroTik Cloud Hosted Router (all versions)
  • Action Required: MikroTik recommends several mitigations: use a strong VPN if the API is exposed to public networks, configure unsuccessful-attempt time ranges for services, connect initially from a trusted LAN port, restrict access to management services from untrusted networks, apply firewall rules to control access, and use long, randomly generated passwords.
  • Timeline: Disclosed on July 28, 2026

Original Article Summary

View CSAF Summary Successful exploitation of this vulnerability could allow attackers to rapidly guess passwords and gain unauthorized system access. The following versions of MikroTik RouterOS and Cloud Hosted Router are affected: RouterOS vers:all/* (CVE-2026-16347) Cloud Hosted Router vers:all/* (CVE-2026-16347) CVSS Vendor Equipment Vulnerabilities v3 8.8 MikroTik MikroTik RouterOS and Cloud Hosted Router Improper Restriction of Excessive Authentication Attempts Background Critical Infrastructure Sectors: Information Technology, Commercial Facilities Countries/Areas Deployed: Worldwide Company Headquarters Location: Latvia Vulnerabilities Expand All + CVE-2026-16347 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. View CVE Details Affected Products MikroTik RouterOS and Cloud Hosted Router Vendor: MikroTik Product Version: MikroTik RouterOS: vers:all/*, MikroTik Cloud Hosted Router: vers:all/* Product Status: known_affected Remediations Mitigation 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. Mitigation Configure the unsuccessful-attempt time range (0.1 to 0.5 seconds) in /ip service for all services, including the API, once available. Mitigation Connect initially from a trusted network (LAN) port only, then configure the router per your security requirements. Mitigation Restrict/limit access to management services from untrusted networks. Mitigation Apply firewall rules to control and restrict access to management services where possible. Mitigation Use long, randomly generated passwords rather than weak or default-simple ones, to keep the brute-force search space impractically large. Mitigation Keep the default randomly generated device password, or replace it with an equally strong one, since minimum complexity isn't enforced by default. Mitigation Users are encouraged to reach out to MikroTik (https://mikrotik.com/support) for further support. https://mikrotik.com/support Relevant CWE: CWE-307 Improper Restriction of Excessive Authentication Attempts Metrics CVSS Version Base Score Base Severity Vector String 3.1 8.8 HIGH CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 4.0 8.7 HIGH 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 Acknowledgments Andre Santos of União Geek reported this vulnerability to CISA Legal Notice and Terms of Use This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy). Recommended Practices CISA recommends users take defensive measures to minimize the risk of exploitation of this vulnerability. Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet. CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures. CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies. CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets. Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies. Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents. No known public exploitation specifically targeting this vulnerability has been reported to CISA at this time. This vulnerability is not exploitable remotely. Revision History Initial Release Date: 2026-07-28 Date Revision Summary 2026-07-28 1 Initial Publication Legal Notice and Terms of Use

Impact

MikroTik RouterOS (all versions), MikroTik Cloud Hosted Router (all versions)

Exploitation Status

No active exploitation has been reported at this time. However, organizations should still apply patches promptly as proof-of-concept code may exist.

Timeline

Disclosed on July 28, 2026

Remediation

MikroTik recommends several mitigations: use a strong VPN if the API is exposed to public networks, configure unsuccessful-attempt time ranges for services, connect initially from a trusted LAN port, restrict access to management services from untrusted networks, apply firewall rules to control access, and use long, randomly generated passwords. Users should keep the default randomly generated password or replace it with a strong one.

Additional Information

This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.

Related Topics: This incident relates to CVE, Vulnerability, Critical.

Related Coverage

NGINX Fixes 5 Flaws, Including Possible RCE and a TLS Bug That May Skip Client-Cert Checks

The Hacker News

NGINX has released updates to address five vulnerabilities, including a significant flaw that has persisted since May 2005. Among these are three memory-related issues that could crash a worker process or potentially allow an attacker to execute arbitrary code, contingent on specific configurations. Additionally, one vulnerability could enable attackers to forge a TLS session, bypassing client certificate checks. These vulnerabilities affect all versions of NGINX since the identified flaw's introduction, making it crucial for users to update promptly. The release of versions 1.30.6 and 1.31.7 on October 14 is a direct response to these security risks, emphasizing the need for users to maintain up-to-date software to protect against exploitation.

Oct 15, 2026

Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing

The Hacker News

Next.js has rolled out an urgent security patch that addresses two serious vulnerabilities allowing unauthenticated remote code execution (RCE) and a high-severity denial-of-service (DoS) issue. The first RCE flaw is linked to React Server Components, while the second involves librsvg, an open-source library used by Next.js for processing SVG images through the sharp package. This update, released on October 14, is crucial for developers using Next.js, as it can prevent attackers from executing malicious code on affected systems. Users should apply this patch promptly to protect their applications from potential exploitation. The vulnerabilities could have serious implications for any web applications relying on Next.js, making swift remediation essential.

Oct 15, 2026

Fake AI Attacks Spread Across US Companies: How MSSPs Can Stop Incidents Early

The Hacker News

A new wave of cyberattacks is targeting US companies through fake AI products. Attackers are mimicking popular AI software to spread malware, hijack browser sessions, and compromise business accounts. Research from ANY.RUN identified over 1,200 instances of these campaigns between April and October 2026, with a significant portion of the attacks aimed at US businesses. This surge in malicious activity is putting additional strain on Managed Security Service Providers (MSSPs), who are struggling to keep up with the growing threat. Companies need to be vigilant about the authenticity of AI tools they use and ensure they have adequate security measures in place to protect against these deceptive tactics.

Oct 15, 2026

Why AI Confidence Is Not Validation

The Hacker News

Artificial Intelligence (AI) is increasingly being used in digital forensics and incident response, but there are growing concerns about the reliability of these tools. As AI systems become more confident in their outputs, practitioners have not yet established effective methods to verify that information. This lack of governance and validation standards poses a risk, as inaccuracies in AI-generated results can lead to significant missteps in cybersecurity efforts. The gap between AI confidence and human verification could result in uncontained errors that may affect broader systems and organizations. Addressing this issue is crucial for ensuring that AI supports rather than undermines cybersecurity practices.

Oct 15, 2026

India Mandates Registered Caller Name Display on 4G and Newer Networks From November 1

The Hacker News

Starting November 1, 2026, the Indian government will require telecom service providers to display the registered names of callers along with their phone numbers for incoming calls. This new regulation aims to help users identify unknown numbers and reduce the volume of spam and fraudulent calls. The Department of Telecommunications issued a circular to enforce this change, indicating a proactive approach to enhance caller transparency. By making it easier for individuals to recognize who is calling, the government hopes to protect citizens from potential scams and unwanted solicitations. This initiative is part of a broader effort to improve telecommunications security and user experience in India.

Oct 15, 2026

GhostAction Compromises About 1,900 GitHub Accounts, Targets Over 30,000 Repositories

The Hacker News

A credential-theft campaign named GhostAction has recently intensified, affecting around 1,900 GitHub accounts. This attack, observed by GitGuardian on October 8 and 9, 2026, targeted over 30,000 repositories linked to approximately 3,000 users and organizations. The attackers aimed to extract sensitive information, specifically 3,174 secrets from public repositories' Continuous Integration (CI) systems. This incident raises significant concerns for developers and organizations using GitHub, as compromised accounts can lead to unauthorized access and potential data breaches. Users are advised to secure their accounts and monitor their repositories for any suspicious activity.

Oct 15, 2026