Description
RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. Because signature verification uses the client-supplied key, an attacker knowing an authorized RSA modulus can supply a key with exponent one, forge a valid signature, and open an SSH command channel as the target user without the private key.This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)
Published: 2026-09-05
Score: 9.2 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

RouterOS fails to compare the full RSA public key when authenticating SSH requests, checking only the key type and modulus but ignoring the exponent. An attacker who knows an authorized RSA modulus can supply a key with an exponent of one, forge a valid signature, and consequently open an SSH command channel as the target user. This allows the attacker to run arbitrary commands with the privileges of the impersonated account, effectively achieving remote code execution on the device.

Affected Systems

The vulnerability affects Mikrotik RouterOS versions older than 6.49.21 for long‑term, 7.23.4 for long‑term, and 7.24.2 for stable releases. Any device running these older releases is susceptible if RSA key authentication is enabled for any user.

Risk and Exploitability

With a CVSS score of 9.2 the vulnerability is considered critical. Although no EPSS score is published, industry advisories have reported active exploitation in the wild. The attack vector is remote, requiring an attacker to establish an SSH session and supply a forged key. If the attacker can obtain the public‑key modulus (e.g., from captive portals or leaked backups), the exploit can be executed without the private key, allowing full impersonation of the target user.

Generated by OpenCVE AI on September 5, 2026 at 21:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Mikrotik RouterOS to at least 6.49.21 for long‑term or 7.23.4 / 7.24.2 for stable releases
  • If an upgrade cannot be performed immediately, restrict SSH access to trusted IP addresses using firewall rules to limit the attack surface
  • Temporarily disable RSA key‑based authentication for highly privileged accounts or rotate the SSH keys until the patch is applied

Generated by OpenCVE AI on September 5, 2026 at 21:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 05 Sep 2026 20:45:00 +0000

Type Values Removed Values Added
Description RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. Because signature verification uses the client-supplied key, an attacker knowing an authorized RSA modulus can supply a key with exponent one, forge a valid signature, and open an SSH command channel as the target user without the private key.This issue was fixed in versions: 6.49.21 (Lont-term), 7.23.4 (Lont-term) and 7.24.2 (Stable) RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. Because signature verification uses the client-supplied key, an attacker knowing an authorized RSA modulus can supply a key with exponent one, forge a valid signature, and open an SSH command channel as the target user without the private key.This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)

Sat, 05 Sep 2026 20:15:00 +0000

Type Values Removed Values Added
Description RouterOS does not compare the complete RSA public key when matching an SSH authentication request to an authorized user key, checking the key type and modulus but omitting the exponent. Because signature verification uses the client-supplied key, an attacker knowing an authorized RSA modulus can supply a key with exponent one, forge a valid signature, and open an SSH command channel as the target user without the private key.This issue was fixed in versions: 6.49.21 (Lont-term), 7.23.4 (Lont-term) and 7.24.2 (Stable)
Title SSH user impersonation possible in Mikrotik RouterOS
First Time appeared Mikrotik
Mikrotik routeros
Weaknesses CWE-347
CPEs cpe:2.3:a:mikrotik:routeros:*:*:*:*:*:*:*:*
Vendors & Products Mikrotik
Mikrotik routeros
References
Metrics cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Mikrotik Routeros
cve-icon MITRE

Status: PUBLISHED

Assigner: CERT-PL

Published:

Updated: 2026-09-05T20:39:06.278Z

Reserved: 2026-07-29T11:59:30.538Z

Link: CVE-2026-67276

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-05T20:17:17.977

Modified: 2026-09-05T21:16:49.387

Link: CVE-2026-67276

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-05T21:30:17Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature