Skip to content
major vulnerability· requires attention

MikroTik RouterOS is widely deployed in networking infrastructure; a remote SSH auth bypass enabling account takeover can disrupt networks and receive broad attention.

Networks

CVE-2026-67276

9.2
Critical
EPSS 0.24%Patch availableSep 6, 2026

SSH auth bypass in MikroTik RouterOS allows account takeover via crafted RSA key.

common questions

Is CVE-2026-67276 being exploited?

Not confirmed. CVE-2026-67276 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-67276?

CVE-2026-67276 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-67276?

Yes. A fix has been recorded for CVE-2026-67276. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-67276 affect?

CVE-2026-67276 affects MikroTik RouterOS (versions prior to 6.49.21, 7.23.4, 7.24.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67276?

Upgrade to 6.49.21, 7.23.4 or 7.24.2+; restrict SSH access and rotate keys.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MikroTik RouterOS (versions prior to 6.49.21, 7.23.4, 7.24.2)
impact

Remote SSH authentication bypass: attacker can open an SSH command channel as a target user without possessing the private key.

action required

Immediate action required

affected versions
Mikrotik RouterOS
  • affected>= 7.24 and < 7.24.2
  • affected>= 7.9 and < 7.23.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free