CVE-2026-67277: MikroTik RouterOS bandwidth-test server leaks memory and crashes
Exploited in the wild High 8.8 EPSS 1.6% MikroTik RouterOS
The RouterOS bandwidth-test (btest) server accepts a related connection before the main session has logged in. An unauthenticated attacker can use it to leak uninitialised kernel memory and, through an integer underflow, make the router restart. CISA added it to the Known Exploited Vulnerabilities catalog on 10 September 2026. Fixed in RouterOS 6.49.21, 7.23.4 and 7.24.2.
- CVE-2026-67277CVE identifier
- 8.8CVSS 4.0 base score (high)
- 2026-09-10added to CISA's exploited list (US federal deadline 2026-09-13)
- 1.6%EPSS: chance of exploitation in the next 30 days (higher than 75% of CVEs)
- 2026-09-05published
What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms
What to do now
- Check whether you run MikroTik RouterOS and which version (commands below).
- Install the fixed version for your system: see “Patch it” below.
- Installing a RouterOS update always reboots the router. On RouterBOARD hardware, run /system routerboard upgrade afterwards and reboot a second time so the matching RouterBOOT firmware is loaded. Plan for two short outages and make sure you have out-of-band or local access in case the router does not come back.
- If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
- Because this flaw is being exploited, also check the server for signs of compromise.
Affected and fixed versions
Affected:
- RouterOS 6.0 before 6.49.21
- RouterOS 7.0 before 7.23.4
- RouterOS 7.24 before 7.24.2
Fixed in:
- RouterOS 6.49.21
- RouterOS 7.23.4
- RouterOS 7.24.2
- Recommended as of 3 Nov 2026: 7.25 (stable), 7.24.6 (long-term) or 6.49.23
Am I affected?
/system resource print # version, architecture-name, board-name
/system package update print # channel, installed-version, latest-version
/system routerboard print # current-firmware vs upgrade-firmware (not on CHR/x86)
/ip service print # which management services are enabled, and from where
/tool bandwidth-server print # enabled: yes means the btest server listens (TCP 2000)
Patch it
Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.
Built from source
# RouterOS CLI (works on v6 and v7; v7 also accepts /system/package/update/...)
# Current releases as of 3 Nov 2026: 7.25 (stable), 7.24.6 (long-term), 6.49.23 (RouterOS 6)
/system backup save name=pre-update
/export file=pre-update
/system package update set channel=long-term # or stable
/system package update check-for-updates
/system package update print # status should say: New version is available
/system package update install # downloads, installs and REBOOTS the router
# after it is back up:
/system resource print # confirm the new version
/system routerboard upgrade # RouterBOARD only: new RouterBOOT firmware
/system reboot # REBOOTS again to load the firmwareGeneral update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.
If you cannot patch yet
- Updating is the fix. MikroTik's hardening guide says to disable the bandwidth server in production: /tool bandwidth-server set enabled=no
- Drop TCP and UDP port 2000 from untrusted networks in the firewall input chain if you must keep btest running.
Look for signs of exploitation
- Unexpected router restarts (check /log print and /system resource print uptime) and bandwidth-test sessions from unknown addresses.
CISA required action: 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.
https://mikrotik.com/supportsec/september-2026-vulnerability/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-67277
Related vulnerabilities
Sources
- CVE-2026-67277 (CVE.org)
- CVE-2026-67277 (NVD)
- CISA KEV entry
- MikroTik security advisory: September 2026 vulnerability (updated 6 Oct 2026)
- CERT Polska: MikroTik RouterOS CVE details
- CERT Polska: Vulnerabilities in MikroTik RouterOS actively exploited (5 Sep 2026)
- MikroTik forum: 6.49.21 long-term is released
- MikroTik forum: 7.23.4 long-term is released
- MikroTik forum: 7.24.2 stable is released
- RouterOS manual: Securing your router
- https://npratley.net/reversing-mikrotiks-silent-patch-the-routeros-7-23-4-fix-they-wouldnt-explain/
- CISA Known Exploited Vulnerabilities catalog
Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.