VulnerabilityPublished 14 Sep 2026Updated 26 Oct 2026

CVE-2026-65405: Apple iOS and iPadOS · An app may be able to determine kernel memory layout

Affects Apple iOS and iPadOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 27 or 26.7 when convenient.

Data as of 29 Oct 2026, 19:15 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	5.5

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 27, 26.7, 15.8

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-f9ph-w48v-6xp9

What to do

Upgrade iOS and iPadOS to 27 or 26.7; macOS to 27, 26.7 or 15.8; tvOS and visionOS and watchOS to 27.

Affected software

Product	Affected	Fixed in
AppleiOS and iPadOS	Affected <27	Fixed in 27
AppleiOS and iPadOS	Affected <26.7	Fixed in 26.7
ApplemacOS	Affected <27	Fixed in 27
ApplemacOS	Affected <26.7	Fixed in 26.7
ApplemacOS	Affected <15.8	Fixed in 15.8
AppletvOS	Affected <27	Fixed in 27

AI-suggested

This vulnerability is fixed in iOS 26.7 and later, iPadOS 26.7 and later, and macOS 15.8 and later. Users and administrators should apply these official updates to remediate the issue.

Description

CVE-2026-65405 is a medium severity vulnerability in Apple iOS and iPadOS where an app may be able to determine the kernel memory layout due to a memory initialization issue. This flaw was addressed by improved memory handling and fixed in iOS 26.7 and later, iPadOS 26.7 and later, and macOS 15.8 and later. The vulnerability does not allow modification or denial of service but may expose sensitive kernel memory layout information.

Impact

An attacker with the ability to run an app on the affected devices could determine the kernel memory layout, which may facilitate further exploitation or bypass of security mechanisms. The vulnerability does not impact integrity or availability. The confidentiality impact is rated high by CVSS but overall severity is medium due to the limited attack vector (local app with user interaction).

Summary

This vulnerability involves a memory initialization flaw in Apple operating systems including iOS, iPadOS, and macOS. An application could exploit this issue to determine the kernel memory layout, potentially aiding further attacks. The issue was resolved by improved memory handling in versions iOS 26.7, iPadOS 26.7, macOS 15.8, and later releases. The CVSS score is 5.5 (medium), reflecting the limited scope of impact (confidentiality impact only). No known exploits in the wild have been reported.

CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 21:38 UTC

WeaknessesCWE-457

Technical details

References

Community reviews

Related threats