CVE-2026-65400
KEVApple macOS Improper Authentication Vulnerability
Description
Apple macOS contains an improper authentication vulnerability that could allow an attacker on the network to authenticate to Screen Sharing without valid credentials.
An authentication issue was addressed with improved state management. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.7.9, macOS Sonoma 14.8.9, macOS Tahoe 26.6.1, macOS Tahoe 26.7. An attacker on the network may be able to authenticate to Screen Sharing without valid credentials.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedAug 6, 2026
Last modifiedOct 24, 2026
Added to KEVAug 18, 2026
Remediation dueAug 21, 2026
References
- support.apple.com/en-us/148170Release NotesVendor Advisory
- support.apple.com/en-us/148171Release NotesVendor Advisory
- support.apple.com/en-us/148172Release NotesVendor Advisory
- support.apple.com/en-us/149035Release NotesVendor Advisory
- support.apple.com/en-us/149042Release NotesVendor Advisory
- seclists.org/fulldisclosure/2026/Aug/36Mailing List
- seclists.org/fulldisclosure/2026/Aug/37Broken Link
- advisories.ncsc.nl/2026/ncsc-2026-0280.htmlThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-65400US Government Resource
0 recent articles mention this CVE
79
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 66 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 1.7% · top 23% of all CVEs
- Weakness
- CWE-287
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.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.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.