CVE-2026-67279
CVE-2026-67279 — SSH Pre-Authentication Rekey State Bypass in MikroTik RouterOS
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)
Published Updated Sources: NVD, Mikrotik (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Sep 25, 2026
EPSS
1%
ahead of 62% of scored CVEs
CVSS base
6.9
medium
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade RouterOS to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
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.
Federal deadline Sep 28, 2026 — passed 11 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Mikrotik | RouterOS | 7.24 to < 7.24.2 | Vulnerable |
| Mikrotik | RouterOS | 7.0.0 to < 7.23.4 | Vulnerable |
| Mikrotik | RouterOS | 6.0.0 to < 6.49.21 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | medium | — | — | Mikrotik (CNA) |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness & attack patterns
- CWE-841
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Sep 25, 2026
Federal deadline
Sep 28, 2026
passed 11 days ago
Ransomware use
Unknown
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 date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable RouterOS.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added to CISA KEV catalog
Sep 25, 2026 · CISA
Added · CVSS 3.1 6.9 (AV:N)
Sep 5, 2026 · NVD
Initial · CVE published
Sep 5, 2026 · NVD
References
13 on the record
- cert.pl/en/posts/2026/09/mikrotik-routeros-cve
Vendor Advisory
- cert.pl/en/posts/2026/09/vulnerabilities-in-mikrotik-routeros-actively-exploited/
Vendor Advisory
- forum.mikrotik.com/t/6-49-21-long-term-is-released/272802
Vendor Advisory
- forum.mikrotik.com/t/7-23-4-long-term-is-released/272801
Vendor Advisory
- forum.mikrotik.com/t/7-24-2-stable-is-released/272800
Vendor Advisory
- mikrotik.com/supportsec/september-2026-vulnerability/
Vendor Advisory
- npratley.net/reversing-mikrotiks-silent-patch-the-routeros-7-23-4-fix-they-wouldnt-explain/
Vendor Advisory
- bishopfox.com/blog/mikrotrick-inside-the-routeros-takeover-chain
Vendor Advisory
Coverage
1 story from the feeds we poll
Elsewhere on this site
- Mikrotikevery CVE for this vendor
- September 2026what else CISA listed
- Unclassifiedsame class
- CWE-841other pages naming this weakness
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 record1
What should defenders know first?
CVE-2026-67279 is SSH Pre-Authentication Rekey State Bypass in MikroTik RouterOS, a medium vulnerability affecting RouterOS from Mikrotik. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.9 describes technical severity, while EPSS 1% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.