Back to Intelligence

CISA KEV Alert: CVE-2026-65400 macOS Authentication Bypass Actively Exploited Alongside SharePoint, vCenter, and Microsoft IKE Flaws — Detection and Remediation Guide

SA
Security Arsenal Team
August 19, 2026
11 min read

On Tuesday, CISA added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog — and every one of them is being exploited in the wild right now. The headline entry is CVE-2026-65400 (CVSS 9.8), an improper authentication vulnerability in Apple macOS that could allow an attacker to bypass authentication controls entirely. Alongside it, CISA flagged critical flaws in Microsoft SharePoint, VMware vCenter Server, and the Microsoft IKE (Internet Key Exchange) implementation — a cross-platform set that touches endpoints, collaboration infrastructure, virtualization management planes, and network security services in a single catalog update.

A 9.8-rated authentication bypass on macOS is not a "wait for the next patch cycle" problem. KEV inclusion means CISA has confirmed active exploitation, which means exploit code and operational playbooks already exist in adversary hands. If you run macOS endpoints, on-prem SharePoint, vCenter, or Windows systems terminating IPsec/IKE tunnels, you are in the blast radius. Federal civilian agencies are under a Binding Operational Directive (BOD 22-01) remediation deadline; every other organization should treat that deadline as its own.

Technical Analysis

What's on the table

PlatformCVECVSSVulnerability Class
Apple macOSCVE-2026-654009.8Improper authentication (authentication bypass)
Microsoft SharePointListed in CISA KEVCriticalUnder active exploitation
VMware vCenter ServerListed in CISA KEVCriticalUnder active exploitation
Microsoft IKE / IPsecListed in CISA KEVCriticalUnder active exploitation

CVE-2026-65400 — macOS improper authentication (CVSS 9.8)

Improper authentication flaws in an operating system are about as bad as it gets defensively. At a 9.8, this scores as a network-reachable, low-complexity issue requiring no privileges and no user interaction. From a defender's perspective, the exploitation model matters more than the exact bug: an attacker who can bypass macOS authentication controls can potentially access services, sessions, or local resources without valid credentials — and from there, establish persistence, escalate privileges, and pivot laterally into the rest of the environment.

What you should expect to observe post-exploitation on a compromised Mac:

  • Abnormal child processes of authentication and system daemons (authd, securityd, loginwindow, opendirectoryd) — shells or scripting interpreters hanging off processes that never normally spawn them.
  • Persistence installation — new LaunchDaemons or LaunchAgents plist files dropped into /Library/LaunchDaemons, /Library/LaunchAgents, or user-level ~/Library/LaunchAgents.
  • Credential access — access to the Keychain (login.keychain-db) or invocation of the security binary with find-generic-password / dump-keychain arguments.
  • Log tampering — macOS unified logs and auth logs being cleared or showing authentication success events with no corresponding legitimate session.

The supporting cast: SharePoint, vCenter, and Microsoft IKE

While full technical details of the other three entries were limited at publication time, the platforms themselves tell you everything about adversary intent:

  • SharePoint remains one of the most reliably targeted enterprise surfaces. Exploitation of SharePoint typically manifests as the IIS worker process (w3wp.exe) spawning unexpected child processes (cmd.exe, powershell.exe, csc.exe for webshell compilation) or dropping .aspx payloads into SharePoint's LAYOUTS directory.
  • vCenter Server is the keys to the virtualization kingdom. Compromise of vCenter means compromise of every VM it manages. Watch vpxd and related vCenter services spawning shells, plus unexpected creation of local accounts or API sessions.
  • Microsoft IKE / IPsec services (IKEEXT) handle VPN key exchange. A flaw here targets remote access infrastructure — the perimeter itself. Abnormal crashes or restarts of the IKEEXT service, or unusual IKE negotiation patterns, warrant immediate review.

Exploitation status

All four vulnerabilities are confirmed actively exploited in the wild — that is the threshold for CISA KEV inclusion. This is not a theoretical risk rating. Under BOD 22-01, federal civilian executive branch agencies must remediate KEV entries by CISA's assigned due date; check each entry in the CISA KEV catalog for the specific deadline. Private-sector organizations should hold themselves to the same clock.

Detection & Response

This is a multi-platform threat, so detection has to span macOS endpoints, Windows servers (SharePoint and IKE), and Linux-based vCenter appliances. The rules below target post-exploitation behavior, which remains detectable even when the initial exploit varies.

Sigma Rules

The following rules cover the three most reliable behavioral signals: macOS authentication daemons spawning interpreters, macOS persistence via LaunchDaemons/LaunchAgents, and the classic SharePoint webshell pattern of w3wp.exe spawning command shells.

YAML
---
title: macOS Authentication Daemon Spawning Shell or Interpreter
id: 3f8c2a71-9b4d-4e6a-b1c7-2d5e8f0a3b6c
status: experimental
description: Detects macOS authentication or directory service daemons spawning shells or scripting interpreters, consistent with post-exploitation activity following an authentication bypass such as CVE-2026-65400.
references:
  - https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/08/05
tags:
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: macos
detection:
  selection_parent:
    ParentImage|endswith:
      - '/authd'
      - '/securityd'
      - '/loginwindow'
      - '/opendirectoryd'
  selection_child:
    Image|endswith:
      - '/bash'
      - '/zsh'
      - '/sh'
      - '/python'
      - '/python3'
      - '/osascript'
      - '/curl'
  condition: selection_parent and selection_child
falsepositives:
  - Rare; MDM agent misconfigurations may trigger review
level: high
---
title: macOS LaunchDaemon or LaunchAgent Persistence Created by Suspicious Process
id: 8a1e4b62-7c3f-4d58-a9e2-1b6c4d7e0f2a
status: experimental
description: Detects creation of LaunchDaemon or LaunchAgent plist files by non-installer processes, a common persistence mechanism following macOS compromise including exploitation of CVE-2026-65400.
references:
  - https://attack.mitre.org/techniques/T1543/001/
author: Security Arsenal
date: 2026/08/05
tags:
  - attack.persistence
  - attack.t1543.001
  - attack.t1543.004
logsource:
  category: file_event
  product: macos
detection:
  selection_path:
    TargetFilename|contains:
      - '/Library/LaunchDaemons/'
      - '/Library/LaunchAgents/'
      - '/LaunchAgents/'
  selection_ext:
    TargetFilename|endswith: '.plist'
  filter_installers:
    Image|endswith:
      - '/installer'
      - '/softwareupdated'
      - '/packagekitd'
  condition: selection_path and selection_ext and not filter_installers
falsepositives:
  - Legitimate enterprise software deployment outside MDM channels
level: high
---
title: SharePoint IIS Worker Process Spawning Command Shell
id: 5c2d7f91-4a8b-4e36-b3d1-9f0a2c5e7b84
status: experimental
description: Detects the SharePoint IIS worker process spawning command shells, PowerShell, or the C# compiler, strongly indicative of webshell deployment or in-memory execution following SharePoint exploitation.
references:
  - https://attack.mitre.org/techniques/T1505/003/
  - https://www.cisa.gov/known-exploited-vulnerabilities-catalog
author: Security Arsenal
date: 2026/08/05
tags:
  - attack.persistence
  - attack.t1505.003
  - attack.execution
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith: '\w3wp.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\csc.exe'
      - '\net.exe'
      - '\whoami.exe'
  condition: selection_parent and selection_child
falsepositives:
  - Rare; some legacy SharePoint solutions invoke command-line tools — verify against deployment records
level: critical

KQL — Microsoft Sentinel / Defender

This query hunts across Windows endpoints and servers (via Defender process events) for the SharePoint exploitation pattern and abnormal IKEEXT service behavior, and separately pulls macOS syslog/CEF telemetry where it is ingested into Sentinel. Run both against a 14-day window.

KQL — Microsoft Sentinel / Defender
// Part 1: SharePoint w3wp spawning shells + IKEEXT anomalies on Windows
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where (InitiatingProcessFileName =~ "w3wp.exe"
        and FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "csc.exe", "net.exe", "whoami.exe"))
        or (InitiatingProcessFileName =~ "svchost.exe"
        and InitiatingProcessCommandLine has "IKEEXT"
        and FileName !in~ ("svchost.exe", "rasmans.dll"))
| project TimeGenerated, DeviceName, InitiatingProcessFileName, FileName,
          ProcessCommandLine, AccountName, InitiatingProcessCommandLine
| order by TimeGenerated desc;

// Part 2: macOS syslog telemetry (via Sentinel Syslog/CEF ingestion) —
// auth daemons spawning interpreters and Keychain access anomalies
Syslog
| where TimeGenerated > ago(14d)
| where Facility == "auth" or ProcessName in~ ("authd", "securityd", "loginwindow", "security")
| where SyslogMessage has_any ("bash", "zsh", "osascript", "dump-keychain", "find-generic-password")
   or (ProcessName =~ "security" and SyslogMessage has "keychain")
| project TimeGenerated, Computer, ProcessName, SyslogMessage, SeverityLevel
| order by TimeGenerated desc

Velociraptor VQL

Use this artifact across macOS and Windows fleets to triage for the persistence and webshell artifacts that survive reboot — LaunchDaemon plists and ASPX files written into SharePoint's LAYOUTS tree. Pair with a netstat() sweep for unexpected listening services on vCenter appliances.

VQL — Velociraptor
-- Hunt for recent persistence and webshell artifacts across the fleet
-- macOS LaunchDaemon/LaunchAgent plists modified in the last 14 days
SELECT FullPath, Mtime, Size,
       read_file(filename=FullPath, length=2048) AS PlistHead
FROM glob(globs=['/Library/LaunchDaemons/*.plist',
                 '/Library/LaunchAgents/*.plist',
                 '/Users/*/Library/LaunchAgents/*.plist'])
WHERE Mtime > now() - 1209600
ORDER BY Mtime DESC

-- Windows: ASPX files written to SharePoint LAYOUTS in the last 14 days (webshell triage)
SELECT FullPath, Mtime, Size
FROM glob(globs=['C:/Program Files/Common Files/microsoft shared/Web Server Extensions/*/TEMPLATE/LAYOUTS/*.aspx',
                 'C:/inetpub/wwwroot/wss/VirtualDirectories/*/_layouts/**/*.aspx'])
WHERE Mtime > now() - 1209600
ORDER BY Mtime DESC

-- Windows: processes spawned by w3wp (SharePoint worker process)
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Name =~ 'w3wp'
   OR CommandLine =~ 'w3wp.exe'

Verification and Hardening Script

Use PowerShell on Windows servers to confirm patch state, check for the SharePoint exploitation artifacts above, and audit the IKEEXT service. For macOS fleets, the Bash section verifies OS build currency and enumerates persistence locations for triage.

PowerShell
# --- Windows: SharePoint + IKE verification and triage ---

# 1. Confirm installed updates (cross-reference against Microsoft's current security update GUIDE for the KEV-listed fixes)
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 15 |
  Format-Table HotFixID, Description, InstalledOn

# 2. Check for recently written ASPX files in SharePoint LAYOUTS (webshell triage)
$cutoff = (Get-Date).AddDays(-14)
$layouts = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions"
if (Test-Path $layouts) {
  Get-ChildItem -Path $layouts -Recurse -Filter *.aspx -ErrorAction SilentlyContinue |
    Where-Object { $_.LastWriteTime -gt $cutoff } |
    Select-Object FullName, LastWriteTime, Length
}

# 3. Audit IKEEXT service health — repeated crashes/restarts may indicate exploitation attempts
Get-EventLog -LogName System -Source "Service Control Manager" -After $cutoff |
  Where-Object { $_.Message -match "IKEEXT" } |
  Select-Object TimeGenerated, EntryType, Message | Format-List

# 4. Confirm IKEEXT is not disabled where IPsec is in use, and capture its current state
Get-Service IKEEXT | Select-Object Name, Status, StartType

# --- macOS (run via MDM or ssh): build check + persistence triage ---
# Execute the Bash block below on macOS endpoints
Bash / Shell
# --- macOS: CVE-2026-65400 verification and triage ---

# 1. Capture current macOS version and build — compare against Apple's security release notes
#    for the build that remediates CVE-2026-65400; any build older than the patched release is vulnerable
sw_vers

# 2. Enumerate LaunchDaemons/LaunchAgents modified in the last 14 days for persistence triage
find /Library/LaunchDaemons /Library/LaunchAgents ~/Library/LaunchAgents \
  -name "*.plist" -mtime -14 -exec ls -la {} \; 2>/dev/null

# 3. Check for pending Apple security updates and install them immediately
softwareupdate --list
# sudo softwareupdate --install --all --restart

# 4. Review recent authentication anomalies in the unified log (last 24 hours)
log show --last 24h --predicate 'process == "authd" OR process == "securityd"' \
  --style compact 2>/dev/null | grep -iE "fail|error|denied" | tail -50

Remediation

  1. Patch immediately — this is a KEV event. Apply Apple's security update addressing CVE-2026-65400 on all macOS endpoints. Verify the installed build against Apple's security releases pagesw_vers output must match or exceed the patched build. Apply the corresponding Microsoft (SharePoint and IKE/IPsec) and VMware (vCenter) security updates per their advisories; do not assume a cumulative update covered it — verify explicitly.
  2. Meet the CISA KEV deadline. Under BOD 22-01, federal agencies must remediate by the due date listed in each KEV catalog entry. Pull the four entries, record the due dates, and treat them as internal SLAs regardless of whether you're a federal agency.
  3. Isolate vCenter from the network. vCenter should never be reachable from general user subnets or the internet. If it is, that is an architecture failure to fix this week, independent of any CVE. Restrict management-plane access to a dedicated jump host.
  4. Restrict SharePoint exposure. On-prem SharePoint should sit behind a VPN or private access layer, not on the public internet. If it must be internet-facing, front it with a WAF and verify all cumulative/security updates are applied.
  5. Hunt before you patch. Active exploitation means some environments are already compromised. Run the detection content above across a minimum 14-day retrospective window before assuming patching closed the incident. Patching removes the vulnerability; it does not remove the attacker.
  6. If you find indicators, treat it as an incident. Preserve memory and disk images on suspected hosts, capture macOS unified logs (log collect), and engage IR before remediation wipes evidence. Authentication-bypass exploitation on macOS in particular warrants credential resets for any account that touched the host, including Keychain-protected material.
  7. Validate EDR coverage on macOS. Too many fleets treat Macs as second-class citizens. Confirm your EDR actually reports process lineage and file events from macOS endpoints — the detections above depend on it.

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.