CVE-2026-67279: Mikrotik RouterOS Improper Enforcement of Behavioral Workflow Vulnerability

Published Sep 5, 2026
·
Updated

Mikrotik RouterOS contains an improper enforcement of behavioral workflow vulnerability that could allow an unauthenticated client to open a session channel and send an exec request. This vulnerability can be chained to achieve unauthenticated exploitation of CVE-2026-86060.

Other sources

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)

— MITRE

Affected Software

5 affected components
Mikrotik RouterOS<6.49.21, <7.23.4, <7.24.2
Mikrotik RouterOS>=6.0<6.49.21
Mikrotik RouterOS>=7.0<7.23.4
Mikrotik RouterOS>=7.24<7.24.2
Mikrotik RouterOS

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MikroTik RouterOS to a version that resolves this vulnerability.

    Fixed in 6.49.21
  2. Upgrade

    Upgrade MikroTik RouterOS to a version that resolves this vulnerability.

    Fixed in 7.23.4
  3. Upgrade

    Upgrade MikroTik RouterOS to a version that resolves this vulnerability.

    Fixed in 7.24.2

Event History

Sep 5, 2026
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeaknessAffected Software
Sep 25, 2026
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

Which RouterOS releases contain the fix?

The issue was fixed in RouterOS 6.49.21 Long-term, 7.23.4 Long-term, and 7.24.2 Stable.

2

What does an attacker need to do to exploit this issue?

An unauthenticated SSH client must request a rekey before attempting user authentication. The server can then enter the connection protocol, allowing the client to open a session channel and submit an exec request.

3

What access could an attacker obtain through the vulnerable SSH service?

The attacker can cause the server to dispatch commands without authentication. This enables creation, overwriting, and reconstruction of files in the RouterOS managed file namespace, including support files with configuration and diagnostic data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203