CVE-2026-67277
Kernel memory disclosure and denial of service in MikroTik RouterOS btest service
Exploited in the wild. In CISA KEV since 2026‑09‑10. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Check your MikroTik RouterOS version and whether the btest service is enabled (and confirm the device is reachable from the internet).
- If you are on a vulnerable version, upgrade to one of the fixed versions: 6.49.21, 7.23.4, or 7.24.2.
- After updating, verify the router is reachable, btest-related functions behave normally, and no related errors/restarts occurred during or after the change.
- If you cannot upgrade right away, follow MikroTik/CISA guidance for available mitigations or consider temporarily disabling the btest service and restricting internet access to only what you need.
What it is
From the CVE record
RouterOS accepts a "related" btest connection before the corresponding primary session has completed authentication. An unauthenticated client can use this state to start an IPv4 UDP test. With "random-data=false", the sender transmits an uninitialized tail from a kernel packet buffer. A separate unchecked, inverted packet-size interval causes unsigned integer underflow, anomalously large fragmented output, and can restart the RouterOS kernel. This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)
In plain language
Written by AI from the recordA MikroTik RouterOS feature called the “btest” service can leak pieces of server memory and crash the router, and it’s being exploited in the real world—so you should patch immediately if your RouterOS is exposed to the internet and btest is enabled.
CVE-2026-67277 is a Kernel memory disclosure and denial of service in MikroTik RouterOS btest service caused by improper handling of an unauthenticated pre-auth state, which allows malformed UDP “test” traffic to trigger uninitialized kernel-buffer data exposure and a kernel restart/DoS; it is listed in CISA KEV with a mitigation due date of 2026-09-13.
If you're affected
- Router downtime and outage
- Sensitive memory disclosure risk
- Loss of network access
- Emergency incident response costs
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2026-09-10.
US federal agencies must remediate by 2026-09-13.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.6% chance of exploitation activity in the next 30 days, which ranks it in the 74th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
15 events over 16 days, from the signal feeds we watch.
- Analysis publishedMikroTik's Newest Router Bugs Were Found by an AI Model. Its Last Two KEV Listings Fueled the Mēris Botnet.
- Patch availableworkaround available, record updated, record updated
- Added to CISA KEVrecord updated
- Record updated
- Record updatedrecord updated
- OpenVAS check addedpublished, weakness classified, att&ck mapped, record updated
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Scored 8.2 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- cert.pl/en/posts/2026/09/mikrotik-routeros-cve
- cert.pl/en/posts/2026/09/vulnerabilities-in-mikrotik-routeros-actively-exploited/
- forum.mikrotik.com/t/6-49-21-long-term-is-released/272802
And 5 more references. See all after sign-in
In the news
- CISA Adds 5 Actively Exploited Artifactory, ScreenConnect, and RouterOS Flaws to KEV
- ⚡ Weekly Recap: Chrome 0-Day, Router Hijacks, Coder Supply Chain Attack and More
- Hackers exploit RouterOS flaws to hijack MikroTik devices without authentication
- Hackers exploit new MikroTik RouterOS flaws to hijack routers
- Уязвимости RouterOS позволяют захватывать маршрутизаторы MikroTik через SSH
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for RouterOS, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI