CVE-2026-67279 — Mikrotik RouterOS Improper Enforcement of Behavioral Workflow Vulnerability
RouterOS SSH enters the connection protocol after a client-requested rekey even though user authentication was never attempted, allowing an unauthenticated client to open a session channel and send an exec request. On affected builds the server dispatches the command, enabling unauthenticated creation, overwrite, and reconstruction of files in the RouterOS managed file namespace, including support files containing configuration and diagnostic data.This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 1% (30-day exploitation probability)+9
- Technical severity (medium)+3
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — cert.pl (NIST National Vulnerability Database)
CISA required action CISA
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.
US federal deadline: Sep 28, 2026 — passed 18 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Mikrotik Routeros).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | cvd@cert.pl via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | CERT-PL via CVE Program (cve.org) e CISA ADP |
| 6.5 | CVSS 3.1 | Medium | 3.9 | 2.5 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- MikroTrick (MikroTik RouterOS SSH takeover chain) PoC mirror - CVE-2026-67279 + CVE-2026-86060 (+67276); for authorized lab testing ★ 4 Sep 26, 2026
- CVE-2026-67279 + CVE-2026-86060 – MikroTrick MikroTik RouterOS SSH Pre-Auth Takeover (CVSS 9.2) | Red/Blue Team suite. 2 tools: Full Exploit (rekey bypass, fd-2 policy swap, full-admin shell, plant, mass scan, SOCKS5/Tor, stealth) & SafeDetect (banner/version audit, IoC guidance, JSON/CSV/HTML). Use ★ 3 Sep 27, 2026
- Laboratory proof of concept and research notes for CVE-2026-67279 on MikroTik RouterOS 6.42. ★ 0 Oct 8, 2026
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.03%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Sep 25, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · mikrotik/routeros
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · mikrotik/routeros
- CVSS changed · 6.5
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
14 on the record
- mikrotik.com/supportsec/september-2026-vulnerability/
- cert.pl/en/posts/2026/09/vulnerabilities-in-mikrotik-routeros-actively-exploi
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- mikrotik.com/supportsec/september-2026-vulnerability
- forum.mikrotik.com/t/7-24-2-stable-is-released/272800
- github.com/advisories/GHSA-pqp3-gjgf-83cf
- npratley.net/reversing-mikrotiks-silent-patch-the-routeros-7-23-4-fix-they-wouldnt
- forum.mikrotik.com/t/6-49-21-long-term-is-released/272802
- cert.pl/en/posts/2026/09/mikrotik-routeros-cve
- nvd.nist.gov/vuln/detail/CVE-2026-67279
- forum.mikrotik.com/t/7-23-4-long-term-is-released/272801
- bishopfox.com/blog/mikrotrick-inside-the-routeros-takeover-chain
- cert.pl/en/posts/2026/09/vulnerabilities-in-mikrotik-routeros-actively-exploi
- npratley.net/reversing-mikrotiks-silent-patch-the-routeros-7-23-4-fix-they-wouldnt
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-103903 MikroTik RouterOS WinBox split-principal authentication bypass allows privilege escalation 3d
- Critical CVE-2026-84411 MikroTik RouterOS Integer Underflow 13d
- High CVE-2026-93345 MikroTik RouterOS < 7.25beta4 Improper Input Validation DoS via BGP Labelled-VPN NLRI 23d
- High CVE-2026-89028 MikroTik RouterOS < 7.24 Heap Corruption via SMB1 SessionSetupAndX 29d
- Medium CVE-2026-56719 MikroTik RouterOS < 7.24 Out-of-Bounds Read via SMB1 SessionSetupAndX 29d
- Medium CVE-2026-89021 MikroTik RouterOS Path Traversal via Container OCI/tar Image Extraction Sep 14, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-67279 is "Mikrotik RouterOS Improper Enforcement of Behavioral Workflow Vulnerability", rated Medium. It affects Routeros (Mikrotik); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 6.5 describes technical severity. EPSS 1.03% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.