CVE-2026-64767: A buffer overflow was addressed with improved bounds checking.
A buffer overflow was addressed with improved bounds checking. This issue is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6. A remote attacker may be able to cause unexpected system termination or corrupt kernel memory.
Security readout for executives and security teams
Plain-English summary
A remotely reachable buffer overflow in macOS may let an unauthenticated attacker crash a Mac or corrupt kernel memory without user interaction. Apple addressed the flaw through improved bounds checking in specified macOS updates. The potential kernel impact and CVSS 9.8 score make delayed patching a serious business risk.
Executive priority
Treat this as an urgent patching priority. Identify unpatched Macs immediately and accelerate deployment using normal change controls, beginning with exposed and critical systems. Absence from KEV lowers certainty about immediate attacks, but it does not offset the severe potential impact or unauthenticated remote attack characteristics.
Technical view
CVE-2026-64767 is a CWE-120 buffer overflow with CVSS 3.1 score 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The supplied record indicates remote, unauthenticated, low-complexity reachability and possible system termination or kernel-memory corruption. It does not identify the affected component, protocol, vulnerable version ranges, or exploitation mechanism.
Likely exposure
Macs running affected macOS branches without Sequoia 15.7.8, Sonoma 14.8.8, or Tahoe 26.6 are the likely concern. The supplied affected-version data is incomplete, listing placeholder values rather than precise vulnerable ranges. Exposure should therefore be determined from installed versions and Apple’s branch-specific advisories.
Exploitation context
The supplied record does not report active exploitation, and the CVE is not identified as present in KEV. No public proof of concept or confirmed attack activity is established by this source bundle. Nevertheless, the stated remote, unauthenticated path and potential kernel-memory corruption create substantial theoretical risk.
Researcher notes
The source bundle attributes the issue to insufficient bounds checking and classifies it as CWE-120. It provides no affected subsystem, attack surface, root-cause detail, or vulnerable-version boundaries. Researchers should avoid inferring a protocol or exploit primitive. Validation should focus on advisory applicability, patch presence, and relevant crash telemetry until Apple publishes more detail.
Mitigation direction
Update macOS Sequoia systems to 15.7.8 or later.
Update macOS Sonoma systems to 14.8.8 or later.
Update macOS Tahoe systems to 26.6 or later.
Prioritize internet-facing, privileged, and business-critical Macs.
Check Apple guidance for unsupported or differently maintained macOS branches.
Validation and detection
Inventory macOS editions and installed versions across managed devices.
Confirm each device reports the applicable fixed release or later.
Review deployment tooling for failed, deferred, or pending updates.
Recheck Apple advisories for clarified affected versions and prerequisites.
Monitor security telemetry for unexplained kernel crashes or repeated system termination.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.