← Back to Vulnerability Reports CVE Intelligence

CVE-2026-67279

MikroTik RouterOS•MEDIUM · CVSS 6.5• In the wild In CISA KEV

What is CVE-2026-67279?

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)

CVSS6.5 NVD 3.1
SeverityMEDIUM
Exploitation In the wild In CISA KEV
EPSS2% · P83
Triage statusActive Exploit
ActionPatch immediately
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CWECWE-841
NVD published2026-09-05
NVD last modified2026-09-26

Timeline

  • 2026-09-05Published to the U.S. National Vulnerability Database (NVD)
  • 2026-09-24First covered in a defend.network daily briefing
  • 2026-09-25Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
  • 2026-09-26NVD record last updated
  • 2026-09-28CISA federal remediation deadline (BOD 22-01)

CISA Known Exploited Vulnerability

Mikrotik RouterOS Improper Enforcement of Behavioral Workflow Vulnerability

Added to KEV2026-09-25
Federal patch deadline2026-09-28
Known ransomware useUnknown

Affected product

MikroTik RouterOS

Remediation Steps

  1. Apply the vendor security update for MikroTik RouterOS as a priority.
  2. Restrict network exposure of the affected service to trusted sources until patched.
  3. Review logs and detections for indicators of exploitation.
  4. Confirm fixed versions against the official vendor advisory before deploying.

Related vulnerabilities

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.