Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-67278: Improper RSA signature verification in MikroTik RouterOS

Published Sep 5, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.3Medium · v4
EPSS0.26%18th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Mikrotik
IdentifiersCVE-2026-67278CWE-347 · Improper Verification of…

CVE-2026-67278 is an improper cryptographic-signature verification vulnerability affecting MikroTik RouterOS 7.x. RouterOS accepts malformed RSA/PKCS#1 v1.5 signatures across RSA-based services, including TLS/X.509 certificate validation and SSH host-key authentication. Its trust store contains a root CA with RSA public exponent e=3, allowing an attacker controlling or redirecting an outbound TLS connection to forge a trusted intermediate certificate using only the root's public certificate. The attacker can then issue certificates for arbitrary hostnames and impersonate TLS servers. The permissive verification also undermines RSA-based SSH authentication.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can defeat TLS server authentication by presenting forged certificates that RouterOS accepts as trusted, enabling server impersonation and man-in-the-middle interception. This compromises the authenticity of affected TLS connections and can expose communications to interception. RSA-based SSH authentication is also undermined, although the precise SSH exploitation conditions and resulting access are not established.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict RouterOS outbound TLS connections to trusted, controlled network paths. Prevent attacker-controlled DNS or routing changes, and apply network segmentation and egress controls to reduce opportunities for TLS interception or redirection. These controls reduce exposure but do not correct signature verification.

Remediation

Patch, then assume compromise.

Upgrade affected RouterOS 7.x installations to 7.23.6 (Long-term), 7.24.3 (Stable), or a later release containing the complete fix. Versions 7.23.4 and 7.24.2 contain incomplete fixes and should not be considered sufficient remediation. Earlier advisory statements listing those releases as fixed conflict with the explicit complete-fix information. RouterOS 6.x is not affected according to the vulnerability-specific description.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MikrotikRouterosoperating_system
FAQ

Frequently asked questions

Is CVE-2026-67278 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-67278?
Yes. As of Oct 9, 2026, Mallory has reports of a public exploit for CVE-2026-67278.
Is there a patch for CVE-2026-67278?
Upgrade affected RouterOS 7.x installations to 7.23.6 (Long-term), 7.24.3 (Stable), or a later release containing the complete fix. Versions 7.23.4 and 7.24.2 contain incomplete fixes and should not be considered sufficient remediation.
What products are affected by CVE-2026-67278?
Mikrotik Routeros.
How severe is CVE-2026-67278?
CVE-2026-67278 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.26% (18th percentile) as of Oct 9, 2026.
Activity feed

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.