ZeroDay Findings
Sign inSign up

Findings

Vulnerability · CVE-2026-67276

MikroTik RouterOS Improper Verification of Cryptographic Signature

Published Sep 5, 2026 · corrected/updated Sep 5, 2026 · MikroTik RouterOS · evidence confidence very high

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) Initial-access exploit intelligence.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-67276 is a unknown public vulnerability record for MikroTik RouterOS. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether MikroTik RouterOS is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: MikroTik RouterOS. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: EPSS 6.5%. CISA lists it as known exploited. Sources contributing to this record: cve_org, epss, vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Confirmed in CISA KEV since Sep 5, 2026. Listed in CISA KEV and VulnCheck KEV.

  • Patch and remediation

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 5, 2026 · VulnCheck KEV

    Detected

    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

  2. Sep 5, 2026 · CISA KEV

    Known exploited

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected

  • vendor MikroTik RouterOSversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2026-67276

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-67276

    30-day exploitation probability 6.5%

    first.org
  • VulnCheck KEVConfirmed exploitationCVE-2026-67276

    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

    vulncheck.com

References