EUVD-2026-49513
GHSA-gg7v-93cr-ghx5
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious app to device
-
DeliveryApp executes locally
-
ExploitTrigger flawed kernel memory-handling path
-
ExecutionRead out-of-bounds kernel memory
-
ImpactExfiltrate leaked kernel data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an attacker-controlled app already running locally on the affected Apple device (iOS/iPadOS 26.6, macOS Sequoia <15.7.8, Sonoma <14.8.8, Tahoe <26.6, tvOS/visionOS/watchOS <26.6); there is no remote or unauthenticated vector. Exploitation is limited by the need to first get code execution on the device (malicious/sideloaded app or a compromised installed app) and by app sandboxing - the flaw discloses kernel memory but does not by itself grant code execution, so it is most useful as one link in a larger jailbreak/privilege-escalation chain rather than a standalone attack. |
| Impact | This is a genuinely moderate-severity local information-disclosure issue, and unusually for the recent Apple batch its metadata is well-calibrated rather than inflated. The CVSS 5.5 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) correctly reflects that exploitation requires code already running on the device (a malicious or compromised app), not remote network reach - AV:L, not AV:N. All corroborating signals agree on low real-world urgency: EPSS is 0.17% (7th percentile), CISA SSVC records Exploitation: none, Automatable: no, and Technical Impact: partial, there is no CISA KEV listing and no public proof-of-concept. The 'Information Disclosure' framing and CWE-200 match the described impact ('An app may be able to disclose kernel memory'), so unlike the sibling use-after-free DoS CVEs in this Apple release wave, the tag is accurate here. The impact is C:H/I:N/A:N - a confidentiality-only leak of kernel memory, which is valuable as a KASLR-defeat / info-leak primitive in a larger exploit chain but is not itself code execution or a crash. Bottom line: real but not urgent; patch in normal cadence. No conflicting signals of note; all sources (Apple, NVD, EUVD, SSVC) are consistent. |
| Exploit ScenarioDerived | A user installs a malicious or trojanized app from a sideloaded source or the App Store; when run, the app abuses the flawed kernel memory-handling path to read kernel memory it should not have access to, leaking pointers or sensitive data (e.g. to defeat KASLR) that feed a follow-on privilege-escalation chain. Exploitation is local and requires the attacker's code to already be executing on the device; no public exploit code or active exploitation has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Kernel memory disclosure in Apple iOS and iPadOS (fixed in 26.6), macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6 and watchOS 26.6 allows a locally running app to read kernel memory that should be inaccessible to it, undermining the isolation boundary between user-space apps and the kernel. The prerequisite is meaningful: an attacker must first get attacker-controlled code executing on the device (a malicious, sideloaded, or compromised app), and the flaw itself yields only disclosure - high confidentiality impact but no integrity or availability impact, so it is best characterized as one link in a larger privilege-escalation or jailbreak chain rather than a standalone compromise. Vendor patches are available for every affected platform; there is no remote or network attack vector, no public exploit code identified at time of analysis, no confirmed active exploitation (CISA SSVC exploitation: none), and EPSS is low at 0.17% (7th percentile), consistent with the moderate 5.5 severity and the local-only, code-execution-gated exploitation model.
RemediationAI
Vendor-released patch: install iOS 26.6 and iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, and watchOS 26.6, as documented in Apple's advisories at support.apple.com/en-us/128066 through 128072 and support.apple.com/en-us/148287; because the flaw affects a shared kernel memory-handling path, every one of these platform updates must be applied - patching only iOS, for example, leaves Macs, Apple TVs, Vision Pro and Apple Watch exposed. No workaround fully removes the defect, since there is no configuration toggle for the underlying kernel interface, so remediation is upgrade-based; the only genuine controlling factor is exploitation's prerequisite of locally executing attacker-controlled code, which means the effective compensating controls are hardening against that prerequisite rather than against the information leak itself. Concretely: enforce App Store-only or otherwise trusted app distribution and use MDM allowlisting to block sideloaded binaries on managed fleets (trade-off: reduced flexibility for developers and power users, and allowlisting requires ongoing maintenance as app inventories change); remove or audit untrusted/sideloaded apps and enterprise-signed builds on high-value devices and monitor for jailbreak indicators, since a jailbroken device voids the sandbox assumptions the leak depends on (trade-off: user friction and potential loss of legitimate tooling); and keep the device updated on the fast lane for OS releases so the app sandbox and kernel mitigations remain current (trade-off: earlier adoption of new OS builds). Network-layer controls such as blocking ports or restricting endpoints provide no benefit here because no remote or network attack vector exists, and because the CVSS vector carries PR:N but AV:L is local-only and the leak grants no code execution by itself, defenders should prioritize patch velocity over emergency network mitigations. EPSS is 0.17% and no public exploit has been identified, so this does not warrant out-of-band response, but the leaked kernel state should still be treated as a chaining primitive in any post-compromise investigation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), manifested here as a memory-handling defect in the Apple kernel that Apple addressed by "improved memory handling" - typically an out-of-bounds read or improperly validated/uninitialized memory access reachable from a sandboxed app's interaction with a kernel interface (syscall, driver/IORegistry surface, or shared memory path). The relevant technology is the XNU kernel and its memory-safety layer, which is supposed to guarantee that data copied back to a user-space caller never includes bytes outside the caller's legitimate buffer; when that guarantee breaks, kernel-resident data - including pointers and structures used to derive kernel address-space layout - becomes readable by an unprivileged process. The CPE data confirms the defect is shared across Apple's entire OS family rather than being platform-specific: cpe:2.3:a:apple:ios_and_ipados, apple:macos, apple:tvos, apple:visionos and apple:watchos are all listed as affected, indicating a common kernel/memory-management code path shipped in the 26.x release train plus the two maintained macOS legacy branches (Sequoia 15.x, Sonoma 14.x). The CVSS vector (AV:L, PR:N, UI:R, C:H/I:N/A:N) and the independent assessment both describe a purely local, confidentiality-only primitive: because the result is information disclosure and not memory corruption, the practical value to an attacker is defeating or weakening kernel address-space randomization and furnishing leaked kernel state to a separate memory-corruption bug, which is why such leaks are routinely chained rather than used in isolation. Exploitation is additionally constrained by app sandboxing and entitlements, so only code already running in a context that can reach the vulnerable interface benefits from the flaw.
Know when Tvos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Local app-supplied code so AV:L; the app is the attacker needing no separate victim action, so UI:N; kernel memory disclosure is confidentiality-only (C:H, I:N, A:N).
Primary rating from Vendor (apple).
CVSS VectorVendor: apple
Lifecycle Timeline
4DescriptionCVE.org
The issue was addressed with improved memory handling. This issue is fixed in iOS 26.6 and iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, watchOS 26.6. An app may be able to disclose kernel memory.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit
An issue was discovered in certain Apple products. Rated high severity (CVSS 7.8), this vulnerability is no authenticati
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
WebKit memory corruption in Safari 18.6 and multiple Apple platforms allows remote code execution when processing malici
WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before 9.2.2 allows remote attackers to execute arbitrar
An issue was discovered in certain Apple products. Rated high severity (CVSS 7.8), this vulnerability is low attack comp
Apple kernel lock state checking flaw allows a malicious application to cause unexpected changes in memory shared betwee
An issue was discovered in certain Apple products. Rated high severity (CVSS 7.8), this vulnerability is no authenticati
Apple kernel memory corruption in multiple operating systems allows a malicious application to cause unexpected system t
Out-of-bounds write (CWE-787) in QtWebEngine before 6.10.1-r2 on Alpine Linux, and in other Chromium-based engines such
WebKit arbitrary code execution via use-after-free memory corruption affects Safari 26.2, iOS/iPadOS 18.7.3 through 26.2
On Broadcom BCM4355C0 Wi-Fi chips 9.44.78.27.0.1.56 and other chips, an attacker can craft a malformed RRM neighbor repo
Exploit-DB