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 affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)
Published: 2026-09-05
Score: 9.2 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Remote Command Execution via SSH impersonation
Action: Immediate Patch
AI Analysis

Impact

RouterOS does not compare the complete RSA public key when validating an SSH authentication request, checking only the key type and modulus while omitting the exponent. Because signature verification uses the key supplied by the client, an attacker who knows the authorized RSA modulus can supply a key with an exponent of one, forge a valid signature, and obtain an SSH session as the target user without needing the private key. This capability allows an attacker to gain SSH access as the impersonated account, thereby enabling execution of arbitrary commands with that account’s privileges.

Affected Systems

The vulnerability affects Mikrotik RouterOS 7.x releases older than 7.23.4 (Long-term) and 7.24.2 (Stable). 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. The EPSS score is 0.25%, indicating a low probability of spontaneous exploitation, yet reports of active exploitation exist 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 7, 2026 at 15:33 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Mikrotik RouterOS to 7.23.4 (Long-term) or 7.24.2 (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 7, 2026 at 15:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 15:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:o:mikrotik:routeros:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Tue, 08 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 07 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
References

Mon, 07 Sep 2026 13:30: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 (Long-term), 7.23.4 (Long-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 affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

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-09T04:26:19.218Z

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

Link: CVE-2026-67276

cve-icon Vulnrichment

Updated: 2026-09-08T14:48:54.363Z

cve-icon NVD

Status : Analyzed

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

Modified: 2026-09-25T14:57:53.150

Link: CVE-2026-67276

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-07T15:45:17Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature