How severe is CVE-2026-86060?

No CVSS score has been assigned to CVE-2026-86060 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-86060?

Affected package information for CVE-2026-86060 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-86060?

No fixed release is recorded for CVE-2026-86060 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-86060 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-86060 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2026-86060 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2026-86060, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-86060?

CVE-2026-86060 has an EPSS (Exploit Prediction Scoring System) score of 6.4%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2026-86060 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-86060 (MikroTik RouterOS Improper Neutralization of Argument Delimiters in a Command Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-09-10. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-09-13. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-86060?

CVE-2026-86060 is classified as CWE-88 (CWE-88). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-86060 published, and has it been updated?

CVE-2026-86060 was published on September 5, 2026 and was last updated on September 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-86060

CVE-2026-86060 is a CWE-88 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-10) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

RouterOS contains an argument-handling flaw in the SSH login path involving usernames that begin with a prohibited character, allowing for the trusted RouterOS policy mask to be changed,…

Published

Sep 5, 2026

Updated

Sep 11, 2026

Affected

1 product

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 20, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-10. Federal agencies were required to remediate by 2026-09-13.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-86060.

EPSS Exploitation Probability

via FIRST.org ↗

6.4%probability of exploitation in next 30 days

Lower Risk+4.54%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

RouterOS contains an argument-handling flaw in the SSH login path involving usernames that begin with a prohibited character, allowing for the trusted RouterOS policy mask to be changed, leading to privilege escalation. Exploitation requires an unauthenticated SSH session to reach the RouterOS login helper.This issue was fixed in versions: 6.49.21 (Long-term), 7.23.4 (Long-term) and 7.24.2 (Stable)

Affected Products

1 product · 3 configurations

routerosmikrotik

≥ 7.24 && < 7.24.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52683remotemultiple

MikroTrick_ 7.24_ 7.24.2_ 7.0.0_ 7.23.4_ 6.0.0_ 6.49.21 - RCE

by DigiProSec · Sep 24, 2026

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-86060 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-86060 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works