VulnerabilityPublished 12 Nov 2025Updated 2 Apr 2026

CVE-2025-43205: Apple iOS and iPadOS · An app may be able to bypass ASLR

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium · fixed in 18.4 : update Apple iOS and iPadOS when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.0Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.

What to do

Affected software

Product	Affected	Fixed in
Apple iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

Organizations and users should promptly apply the security updates released by Apple that fix this vulnerability: iOS 18.4, iPadOS 18.4 and 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, and watchOS 11.4. Beyond patching, organizations should enforce strict app vetting and limit installation of apps from untrusted sources to reduce the risk of local exploitation. Employing Mobile Device Management (MDM) solutions to control app permissions and monitor device integrity can help detect suspicious activity. Additionally, leveraging runtime protections such as sandboxing and mandatory code signing on Apple devices further reduces the attack surface. Security teams should monitor for unusual local app behavior that might indicate attempts to exploit memory vulnerabilities. Regularly updating all Apple devices and educating users about the risks of installing unauthorized apps are essential steps. Finally, integrating this vulnerability into threat modeling and incident response plans will prepare organizations to respond quickly if exploitation attempts arise.

Description

An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. An app may be able to bypass ASLR.

Impact

The primary impact of CVE-2025-43205 is the potential bypass of ASLR, a critical security mitigation that protects against memory corruption exploits. By defeating ASLR, attackers gain the ability to predict memory addresses, which significantly increases the likelihood of successful exploitation of other vulnerabilities such as buffer overflows or use-after-free bugs. Although this vulnerability alone does not allow direct code execution or system compromise, it lowers the barrier for attackers to develop more sophisticated exploits. Organizations relying on Apple devices, especially those handling sensitive data or operating in high-security environments, face increased risk if this vulnerability is unpatched. Attackers with local access—such as malicious apps installed on devices—could leverage this flaw to gather memory layout information, potentially leading to further compromise. The lack of required user interaction and privileges makes it easier for attackers to exploit once local access is obtained. The broad range of affected Apple platforms means that enterprises with mixed Apple device deployments are at risk. However, the absence of known exploits in the wild and the medium severity rating suggest the immediate threat is moderate but should not be ignored.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
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 3 Apr 2026, 01:38 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats