Skip to main content
Mallory
CriticalVulnerability

CVE-2026-64696: Remote kernel memory corruption in Apple SMB

Published Jul 27, 2026 · Updated 21 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.72%55th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apple
IdentifiersCVE-2026-64696CWE-787

CVE-2026-64696 is a memory-handling vulnerability in the SMB component of Apple macOS. The flaw was addressed through improved memory handling in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, and macOS Tahoe 26.6. A remote user may be able to trigger the vulnerability and cause unexpected system termination or corrupt kernel memory. The issue is a remote kernel-corruption bug affecting the SMB subsystem, indicating that malformed or otherwise hostile SMB network input can reach vulnerable kernel-level memory operations and destabilize the system.

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 may allow a remote attacker to crash the affected system or corrupt kernel memory. The confirmed impact is denial of service through unexpected system termination and kernel-memory corruption leading to system instability. Because the flaw affects kernel memory, secondary consequences could include broader reliability and security impact, but the available information does not confirm code execution or privilege escalation for this CVE.

Mitigation

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

Apply the vendor security updates on affected macOS systems. If immediate patching is not possible, reduce exposure of SMB services to untrusted networks and restrict remote access paths that can reach the SMB subsystem, although no official workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade affected systems to a fixed release: macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, or macOS Tahoe 26.6, as applicable. The vendor indicates the issue was resolved by improved memory handling in the SMB component.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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-64696 exploited in the wild?
As of Oct 27, 2026, Mallory has no reports of CVE-2026-64696 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-64696?
As of Oct 27, 2026, Mallory has found no public exploit for CVE-2026-64696.
Is there a patch for CVE-2026-64696?
Upgrade affected systems to a fixed release: macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, or macOS Tahoe 26.6, as applicable. The vendor indicates the issue was resolved by improved memory handling in the SMB component.
What products are affected by CVE-2026-64696?
Apple Macos.
How severe is CVE-2026-64696?
CVE-2026-64696 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.72% (55th percentile) as of Oct 27, 2026.
Activity feed

Recent activity

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

View more in app →
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 malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.