CISA has added five vulnerabilities affecting JFrog Artifactory, ConnectWise ScreenConnect, and MikroTik RouterOS to its Known Exploited Vulnerabilities (KEV) catalog, confirming that all five are being actively exploited in the wild. The headline entry, CVE-2026-42016 (CVSS 8.1), is an incorrect authorization flaw — a bug class that lets attackers reach functionality or data they should never touch, often without valid credentials.
If your organization runs any of these three products, treat this as an incident-adjacent event, not a routine patch cycle. KEV inclusion means exploitation is confirmed, not theoretical. Artifactory sits at the heart of your software supply chain, ScreenConnect is a remote access tool that hands an attacker interactive control of endpoints, and RouterOS runs on network edge devices that are notoriously difficult to monitor. Each of these is a high-value target, and the combination suggests threat actors are working the full stack: build systems, remote access infrastructure, and network perimeter.
Under Binding Operational Directive (BOD) 22-01, federal civilian agencies face a mandated remediation deadline for KEV entries. Private-sector organizations should hold themselves to the same clock — the window between KEV listing and mass scanning by commodity actors is measured in days.
Technical Analysis
CVE-2026-42016 — Incorrect Authorization (CVSS 8.1)
The only fully disclosed identifier in this batch, CVE-2026-42016 carries a CVSS score of 8.1 and is described as an incorrect authorization vulnerability. From a defender's perspective, this bug class (CWE-863) is dangerous precisely because it does not look like an attack in transit: there is no malformed payload, no injection string, no signature-friendly exploit marker. The attacker makes syntactically legitimate requests and the application fails to verify that the requester is permitted to perform the action.
In the context of JFrog Artifactory — a binary repository manager that stores build artifacts, container images, and packages — an authorization bypass has supply-chain implications that go well beyond data theft:
- Artifact tampering: An attacker who can write to repositories without proper authorization can poison artifacts that downstream builds consume, replicating the mechanics of classic supply-chain compromise.
- Unauthenticated or low-privilege read access to internal packages, which frequently embed credentials, API keys, and internal service endpoints in configuration files.
- Repository configuration manipulation, including modifying permissions, adding users, or redirecting virtual repositories to attacker-controlled upstreams.
ConnectWise ScreenConnect
ScreenConnect is a remote monitoring and management (RMM) platform, and RMM tooling has become one of the most abused categories in intrusion operations. Exploited ScreenConnect flaws typically allow authentication bypass or unauthorized session creation, after which the attacker inherits the tool's native capabilities: interactive desktop control, file transfer, and — critically — the ability to execute commands on managed endpoints through a trusted, often allow-listed channel. Post-exploitation via ScreenConnect routinely appears as the ScreenConnect client service spawning command interpreters, downloading payloads, or establishing sessions outside business hours. Because the tool is legitimate software, EDR coverage is frequently weaker and firewall rules explicitly permit its traffic.
MikroTik RouterOS
RouterOS runs on MikroTik routers and switches commonly deployed at branch offices, MSP customer sites, and network edges. Historically exploited RouterOS flaws enable remote code execution, credential extraction, or full device takeover. A compromised RouterOS device gives an attacker:
- A traffic interception and manipulation point (BGP/DNS redirection, TLS interception where keys are installed)
- A persistent foothold that survives endpoint remediation — routers rarely get reimaged during IR
- A pivot and C2 relay, often using the device's own scripting and scheduling features for persistence
RouterOS devices have minimal native logging forwarded to SIEMs in most environments, which is why edge-device compromise so often goes undetected for months.
Exploitation Status
All five vulnerabilities are listed in the CISA KEV catalog, which by definition requires reliable evidence of active exploitation in the wild. This is not a watch-list; it is confirmed hostile use. Security teams should assume scanning and exploitation attempts are already reaching internet-facing instances of these products and prioritize accordingly.
Detection & Response
The detections below target observable behaviors associated with exploitation of these three platforms: unauthorized API interaction with Artifactory, abuse of the ScreenConnect client service for command execution, and post-compromise configuration changes on RouterOS devices.
Sigma Rules
---
title: ScreenConnect Client Spawning Command Interpreter or Scripting Engine
id: 3f8a2c41-7b1e-4d59-a2c6-9e1f4b7d8a30
status: experimental
description: Detects the ConnectWise ScreenConnect client service spawning command shells, scripting engines, or download utilities. Post-exploitation of ScreenConnect flaws routinely hands attackers an interactive session, observable as the client service parent process launching cmd, PowerShell, or LOLBins on managed endpoints.
references:
- https://thehackernews.com/2026/09/cisa-adds-5-actively-exploited.html
- https://attack.mitre.org/techniques/T1219/
author: Security Arsenal
date: 2026/09/15
tags:
- attack.command_and_control
- attack.t1219
- attack.execution
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\ScreenConnect.ClientService.exe'
- '\ScreenConnect.WindowsClient.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
condition: selection_parent and selection_child
falsepositives:
- Legitimate technician remote sessions — validate against change tickets and ScreenConnect session logs for the host and time window
level: high
---
title: Suspicious JFrog Artifactory API Access Patterns
id: 8c4d1e92-6a3f-4b27-9d05-2f7c8e1a4b96
status: experimental
description: Detects web requests to Artifactory endpoints associated with administrative and security configuration functions from user agents inconsistent with normal CI/CD tooling. Incorrect authorization flaws (CWE-863, e.g. CVE-2026-42016) are exercised with syntactically valid requests, so detection focuses on sensitive endpoint access paired with anomalous clients rather than exploit payloads.
references:
- https://thehackernews.com/2026/09/cisa-adds-5-actively-exploited.html
- https://attack.mitre.org/techniques/T1190/
author: Security Arsenal
date: 2026/09/15
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection_uri:
cs-uri-stem|contains:
- '/artifactory/api/security/'
- '/artifactory/api/system/'
- '/ui/api/v1/ui/auth/'
- '/artifactory/api/repositories'
selection_method:
cs-method:
- 'PUT'
- 'POST'
- 'DELETE'
filter_known_clients:
cs-user-agent|contains:
- 'JFrog'
- 'Artifactory'
- 'jfrog-cli'
- 'Maven'
- 'Gradle'
- 'docker'
- 'npm'
condition: selection_uri and selection_method and not filter_known_clients
falsepositives:
- Administrators using the REST API from scripts with generic agents (curl/python-requests) — baseline and allow-list known admin source IPs
level: medium
---
title: MikroTik RouterOS Account or Configuration Change Followed by Egress Connection
id: 5b2e7a14-3d9c-4f81-b6e0-1c4a9d2f7e53
status: experimental
description: Detects Windows endpoints establishing outbound connections to MikroTik management services (Winbox 8291, SSH, API 8728/8729) from hosts that are not known network administration stations. Post-exploitation of RouterOS flaws frequently involves operators or tooling connecting back to reconfigure the device, create users, or pull credentials.
references:
- https://thehackernews.com/2026/09/cisa-adds-5-actively-exploited.html
- https://attack.mitre.org/techniques/T1021/
author: Security Arsenal
date: 2026/09/15
tags:
- attack.lateral_movement
- attack.t1021
logsource:
category: network_connection
product: windows
detection:
selection_port:
DestinationPort:
- 8291
- 8728
- 8729
filter_admin_hosts:
Image|endswith:
- '\winbox.exe'
condition: selection_port and not filter_admin_hosts
falsepositives:
- Network management platforms polling RouterOS API ports — allow-list the management subnet
level: medium
KQL — Microsoft Sentinel / Defender
This query hunts for the two most actionable behaviors: ScreenConnect client service spawning execution tooling on endpoints, and connections to MikroTik management ports from unexpected sources. It assumes Defender for Endpoint device tables plus Syslog/CEF ingestion for network device telemetry.
let Lookback = 14d;
// Stage 1: ScreenConnect client service spawning shells or LOLBins
let ScreenConnectAbuse = DeviceProcessEvents
| where Timestamp > ago(Lookback)
| where InitiatingProcessFileName in~ ("ScreenConnect.ClientService.exe", "ScreenConnect.WindowsClient.exe")
or ProcessCommandLine has_any ("ScreenConnect")
| where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","mshta.exe","wscript.exe","cscript.exe","rundll32.exe","certutil.exe","bitsadmin.exe","curl.exe")
| project SC_Time=Timestamp, DeviceName, FileName, ProcessCommandLine, InitiatingProcessFileName, AccountName, ReportId;
ScreenConnectAbuse;
// Stage 2: Connections to MikroTik management ports from non-admin hosts
DeviceNetworkEvents
| where Timestamp > ago(Lookback)
| where RemotePort in (8291, 8728, 8729)
| where ActionType == "ConnectionSuccess"
| summarize Connections=count(), DistinctTargets=dcount(RemoteIP), FirstSeen=min(Timestamp), LastSeen=max(Timestamp) by DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName
| order by Connections desc;
// Stage 3: RouterOS syslog indicators of unauthorized config/user changes (requires Syslog/CEF forwarding)
Syslog
| where TimeGenerated > ago(Lookback)
| where SyslogMessage has_any ("user added", "logged in", "configuration changed", "script", "scheduler")
| where Computer has_any ("mikrotik", "routeros") or Facility == "system"
| project TimeGenerated, Computer, HostIP, SyslogMessage
| order by TimeGenerated desc;
Velociraptor VQL
Use this artifact to sweep your fleet for evidence of ScreenConnect client abuse and unexpected outbound sessions to router management ports — a fast triage step before deeper IR scoping.
-- Hunt for ScreenConnect client processes spawning execution tooling
-- and for established connections to MikroTik management ports
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)ScreenConnect'
OR CommandLine =~ '(?i)screenconnect'
-- Correlate with live network connections to router management services
SELECT Pid, Name, Family, Type, LocalAddress, LocalPort, RemoteAddress, RemotePort, Status
FROM netstat()
WHERE RemotePort IN (8291, 8728, 8729, 22, 23)
AND Status =~ 'ESTAB'
AND RemoteAddress !~ '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)' -- flag external router management
Remediation & Verification Script
The following PowerShell script inventories ScreenConnect server/client versions on Windows systems and checks RouterOS reachability for follow-up, while the Bash section verifies Artifactory version and recent administrative API activity from the application logs. Run under an elevated administrative context; adapt paths to your deployment.
# --- ScreenConnect version and service inventory (Windows endpoints/servers) ---
Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -match 'ScreenConnect|ConnectWise Control' } |
Select-Object DisplayName, DisplayVersion, InstallDate | Format-Table -AutoSize
# Flag any ScreenConnect client service instances for version verification
Get-Service -ErrorAction SilentlyContinue | Where-Object { $_.DisplayName -match 'ScreenConnect' } |
Select-Object Name, DisplayName, Status, StartType
# Pull the binary version directly for comparison against the vendor's fixed release
Get-ChildItem 'C:\Program Files (x86)\ScreenConnect Client*',
'C:\Program Files\ScreenConnect*' -Recurse -Filter *.exe -ErrorAction SilentlyContinue |
Select-Object FullName, @{N='FileVersion';E={$_.VersionInfo.FileVersion}} | Format-Table -AutoSize
# --- Network sweep: which hosts can reach MikroTik management ports? ---
1..254 | ForEach-Object {
$target = "192.168.1.$_" # adjust subnet
foreach ($port in 8291,8728,8729) {
if (Test-NetConnection -ComputerName $target -Port $port -InformationLevel Quiet -WarningAction SilentlyContinue) {
Write-Output "EXPOSED: $target : $port"
}
}
}
# --- JFrog Artifactory: confirm running version and recent admin-plane activity ---
# 1. Report the deployed version (compare against the fixed release in JFrog's advisory)
curl -s -u "${ARTIFACTORY_USER}:${ARTIFACTORY_TOKEN}" \
https://artifactory.example.com/artifactory/api/system/version | jq .
# 2. Review access logs for security/admin API calls from non-CI sources (last 24h)
grep -E '/api/(security|system)/' /var/opt/jfrog/artifactory/log/access.log \
| awk '{print $1, $6, $7, $8}' | sort | uniq -c | sort -rn | head -50
# 3. Hunt for artifact writes outside CI service accounts (potential poisoning)
grep -E 'PUT|DEPLOY' /var/opt/jfrog/artifactory/log/access.log \
| grep -viE 'ci-service|jenkins|github-actions' | tail -100
# --- MikroTik RouterOS: version check and account/persistence audit (run via SSH) ---
ssh admin@router.example.com "/system resource print; /system package print"
ssh admin@router.example.com "/user print detail; /system scheduler print detail; /system script print detail"
# Disable unused management surfaces
ssh admin@router.example.com "/ip service disable api,api-ssl,ftp,telnet,www; /ip service set winbox address=10.0.99.0/24"
Remediation
-
Identify and isolate exposed instances immediately. Enumerate every Artifactory, ScreenConnect, and RouterOS asset in your environment, including shadow instances stood up by development teams and MSP-managed equipment. Confirm which are internet-reachable — these are the priority targets. Shodan/Censys exposure checks against your external ranges take minutes and close the most common gap.
-
Apply vendor fixes within the CISA KEV window. Pull the current fixed-version guidance directly from the vendor advisories: JFrog's security advisories page for the Artifactory CVE-2026-42016 fix, ConnectWise's security bulletin for the ScreenConnect release, and MikroTik's download/changelog portal for the patched RouterOS train. CISA's KEV entry sets a due date for federal agencies under BOD 22-01 — adopt that same date internally. If your vulnerability management SLA for KEV-listed CVEs isn't already tighter than your standard SLA, change that today.
-
If patching is delayed, reduce the attack surface. For Artifactory: restrict access to trusted networks/VPN, enforce SSO with MFA, and audit anonymous access settings (
/api/system/configuration). For ScreenConnect: confirm MFA is enforced on all technician accounts and restrict the server interface to known management networks. For RouterOS: disable all unused services (API, API-SSL, FTP, Telnet, WWW), restrict Winbox/SSH to a management VLAN, and rotate all device credentials. -
Hunt before you patch. Active exploitation means the compromise may predate your fix. Review Artifactory access logs for unauthorized administrative API calls and unexpected artifact uploads, ScreenConnect session logs for connections from unfamiliar IPs or outside business hours, and RouterOS for rogue users, scheduler entries, and scripts. Any positive finding converts this from a patch exercise into an incident response engagement — preserve logs before upgrading, since upgrades can destroy evidence.
-
Rotate credentials on any potentially exposed system. This includes Artifactory access tokens and service account passwords, ScreenConnect technician credentials, RouterOS admin accounts, and — critically — any credentials stored in artifacts or flowing through a potentially compromised router.
-
Close the monitoring gap on edge devices. Forward RouterOS syslog to your SIEM, alert on configuration changes and new user creation, and baseline which internal hosts legitimately communicate with router management ports. Edge device telemetry is the single most common blind spot in KEV-driven intrusions.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.