Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-65400: Authentication Bypass in Apple macOS Screen Sharing

Published Aug 6, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS18.1%97th percentile
CISA KEVYesAdded Aug 18, 2026
In the wildActivePer CISA KEV
Vendor
Apple
IdentifiersCVE-2026-65400CWE-287 · Improper Authentication

CVE-2026-65400 is an improper-authentication vulnerability in Apple macOS Screen Sharing Server. Incorrect authentication-state management can allow a network attacker to establish a Screen Sharing session without valid credentials or user interaction. Apple addressed the issue through improved state management. The exact packet-level trigger is not established, and the vulnerability is distinct from an earlier Screen Sharing stale-return authentication bypass and the post-authentication authorization flaw CVE-2026-43760. Successful exploitation can expose privileged Screen Sharing functionality and has been associated with root-level compromise. The vulnerability is actively exploited and is listed in CISA's Known Exploited Vulnerabilities catalog.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits unauthorized remote access to an affected Mac through Screen Sharing. Exposed privileged file-transfer functionality can support sensitive-file access, privileged file writes, persistence, and subsequent code execution, subject to applicable macOS protections. Observed compromises obtained root access, installed XMRig to mine Monero, established additional SSH access and persistent execution, deleted logs, and modified firewall configuration. These outcomes threaten system confidentiality, integrity, and availability; root code execution is a possible consequence of the compromise rather than an inherently demonstrated direct execution primitive in the authentication bypass itself.

Mitigation

If you can’t patch tonight, do this now.

Disable Screen Sharing where it is unnecessary. Block untrusted access to TCP port 5900 and remove direct Internet exposure. Where remote administration is required, restrict Screen Sharing to trusted, segmented management networks through VPNs, firewall allowlists, or controlled jump hosts. Review previously exposed vulnerable Macs for signs of compromise. Changing a VNC password alone does not address the authentication-state-management flaw.

Remediation

Patch, then assume compromise.

Install the latest compatible macOS security update. Fixed releases include macOS Sonoma 14.8.9, macOS Sequoia 15.7.9, macOS Tahoe 26.6.1 and 26.7, and macOS Golden Gate 27. Verify update deployment across affected assets and prioritize network-exposed Macs. For potentially compromised systems, preserve evidence, isolate affected hosts, investigate unauthorized SSH access, LaunchDaemon persistence, privileged file changes, and altered firewall settings, and remove unauthorized access mechanisms and payloads. Rotate affected credentials after establishing the scope of compromise. Patching or removing only a cryptocurrency miner does not eliminate previously established attacker persistence.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-65400Repository contains a standalone Python exploit PoC and one auxiliary Bash helper script. The main file, CVE-2026-65400.py, implements a network exploit against Apple Screen Sharing over the RFB/VNC protocol. It connects to a target on TCP/5900, performs an RFB handshake using version string 'RFB 003.889', selects Apple SRP security type 36, and sends a crafted oversized SRP frame length intended to bypass authentication. After the bypass, the script uses Apple’s file-copy protocol message type 0x22 to perform arbitrary file operations. The exploit supports three practical modes described in the code and README: read arbitrary files from the target, write arbitrary files to the target, and execute code indirectly by writing a shell script plus a root cron entry. The RCE path is operational rather than just demonstrative because it includes a concrete payload and a built-in listener thread for interactive shell handling, but it is constrained by target configuration: SIP must be disabled for the cron-based persistence/execution path to work. Repository structure is minimal: .gitignore, the Python exploit, LICENSE, README, and get-svn.sh. README provides extensive usage examples, including sensitive file targets and persistence-oriented write targets. get-svn.sh is unrelated to exploitation of the CVE itself; it is a utility for sparse-downloading GitHub folders and then piping a remote gist into bash for cleanup. No evidence suggests the repository is fake; it is a real exploit PoC with offensive file read/write and reverse-shell capabilities.HORKimhab · Disclosed Aug 18, 2026 · python · bash · network · web · fileOperationalCVE-2026-65400-pocThis repository is a small standalone Python proof-of-concept for CVE-2026-65400 affecting Apple macOS Screen Sharing / Apple Remote Management (screensharingd). The repo contains one executable code file (poc_screensharing.py), a README with vulnerability background, usage, affected versions, and mitigation guidance, plus standard LICENSE and .gitignore files. The exploit is a real network-based pre-authentication exploit, not merely a detector. It connects to the target's RFB/VNC-compatible Screen Sharing service on TCP 5900, verifies the server speaks RFB, negotiates protocol version 'RFB 003.889', checks whether the server offers SRP security type 36, and then sends a crafted SRP step-1 message together with a malformed oversized blob. The blob is built by build_read_blob() and contains a poisoned declared length plus a StartFileSend-style request for an attacker-supplied file path. According to the code and README, this abuses a stale-success condition in the authentication state machine so the connection is treated as authenticated before credentials are validated. Once the bypass succeeds, the script reads post-auth file-copy messages from the server and collects file data chunks (kind 102 / DATA) until an end marker (kind 104 / END). It then prints the number of bytes read, a SHA-256 hash, and the raw file contents to stdout. The PoC is intentionally limited to read-only behavior: it does not attempt persistence, command execution, file writes, or shell deployment, although the README states the underlying vulnerability could enable arbitrary file write and eventual RCE. Operationally, the exploit includes retry logic because the bug is described as heap-racy. It stops early if the host appears patched or non-targeted, specifically when SRP type 36 is absent or SecurityResult is non-zero. The user can configure target IP, file path, port, username used in the SRP step-1 frame, retry count, and timeout. Overall, this is an operational PoC demonstrating unauthenticated remote root-level file read against vulnerable macOS Screen Sharing deployments.panchocosil · Disclosed Aug 21, 2026 · python · markdown · networkOperationalCVE-2026-65400The repository contains a README and one Python entry point, exploit.py. The script is a standalone operational exploit, not a module for Metasploit, Nuclei, or another recognized framework. It connects to an operator-supplied TCP target, performs an RFB 3.889 negotiation, requires the server to advertise SRP security type 36, then sends an SRP step-1 frame concatenated with a deliberately malformed/oversized file-transfer blob. The blob uses a poisoned big-endian length and filler PointerEvent records, apparently intended to win a timing-dependent parser/authentication race. The code implements separate builders for privileged read and write file-transfer operations. Read mode requests an arbitrary UTF-8 path and returns raw bytes, hashes the result with SHA-256, and optionally saves it to a local output file. Write mode packages destination-directory metadata, item information, filename, Unix file mode, and local file contents in 64 KiB transfer chunks. The README describes post-exploitation uses: collecting login, SSH, browser, and other protected data through root-context reads; overwriting privileged helpers or launchd-managed content with writes; and gaining persistence or execution when the replaced program is subsequently launched. It does not embed a reverse shell or a fixed command payload; code-execution outcomes require the operator to supply malicious file content and choose a target executable or launchd path. The exploit is explicitly retry-based because failures are expected from the race condition, with a default VNC port of 5900 and configurable timeout, retry count, username, file mode, output path, and local write source. The supplied content identifies CVE-2026-65400 and claims it affects macOS, but provides no specific macOS release range.acheong08 · Disclosed Aug 22, 2026 · python · markdown · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleMacosoperating_system
FAQ

Frequently asked questions

Is CVE-2026-65400 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 18, 2026.
Is there a public exploit for CVE-2026-65400?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-65400, the earliest disclosed Aug 18, 2026.
Is there a patch for CVE-2026-65400?
Install the latest compatible macOS security update. Fixed releases include macOS Sonoma 14.8.9, macOS Sequoia 15.7.9, macOS Tahoe 26.6.1 and 26.7, and macOS Golden Gate 27.
What products are affected by CVE-2026-65400?
Apple Macos.
How severe is CVE-2026-65400?
CVE-2026-65400 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 18.1% (97th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

225 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+28 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware14Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity164Community discussion across Reddit, Mastodon, and other social sources.