SharePoint RCE and MikroTik RouterOS Flaws Actively Exploited in the Wild

CVE-2026-65660 is an improper control of code generation (CWE-94) flaw in Microsoft Office SharePoint Server that allows an authenticated, low-privilege attacker to inject and execute arbitrary code over a network. The bug is triggered after login by sending crafted input that SharePoint processes and executes, so any account with basic access to the SharePoint site — including a standard user — is a viable attack path. Successful exploitation yields remote code execution on the SharePoint server with the privileges of the SharePoint service account, threatening full compromise of confidentiality, integrity, and availability (CVSS 8.8). Notably, Microsoft initially classified the flaw as spoofing before it was recharacterized as authenticated RCE, and Canada's Cyber Centre has issued advisory AL26-023 about it. A public proof-of-concept exists on GitHub, but the issue is not in CISA's KEV catalog and there are no confirmed reports of in-the-wild exploitation yet, though EPSS (1.2%, 67th percentile) suggests above-average likelihood of attempted exploitation.

Do: Apply Microsoft's security update for SharePoint Server from the corresponding Patch Tuesday release as soon as possible, prioritizing any server reachable from the internet or exposed to broad internal user populations. Because exploitation only requires an authenticated low-privilege account, review recent SharePoint audit logs for anomalous behavior by ordinary users (unexpected page/app modifications, unusual requests preceding process activity), and enforce least-privilege access so standard accounts cannot reach sensitive site collections. Verify patch levels across all SharePoint farms, including pre-production and forgotten servers, and monitor Microsoft's advisory and the Canadian Cyber Centre's AL26-023 for updates on active exploitation.

CVE-2026-86060 is an argument-injection flaw (CWE-88) in MikroTik RouterOS's SSH login path: when a login supplies a username beginning with a prohibited character, the RouterOS login helper mishandles the argument, allowing the trusted RouterOS policy mask to be changed and privileges to be escalated. An unauthenticated attacker only needs the ability to reach the router's SSH service, since exploitation happens during the SSH login process itself. By altering the policy mask the attacker gains elevated rights on the device, and news reports indicate attackers have used this technique — including logins with usernames such as '-2' — as part of chains that take over routers without needing a password. Any RouterOS deployment running versions before the fixes (6.49.21 Long-term, 7.23.4 Long-term, 7.24.2 Stable) with SSH enabled or reachable is affected, with internet-exposed SSH at highest risk. Multiple outlets report the RouterOS flaws are being actively exploited in the wild, although no public proof-of-concept is known and the flaw is not yet in CISA KEV.

Do: Upgrade RouterOS to 6.49.21 (Long-term), 7.23.4 (Long-term) or 7.24.2 (Stable) as applicable. Until patched, restrict SSH (TCP 22) to trusted management networks or disable the SSH service if unused, and review authentication logs and user/group policy settings for tampering — reports indicate attackers log in with usernames beginning with '-' (e.g., '-2').