CVE-2025-24194VulnerabilityPublished 31 Mar 2025Updated 2 Apr 2026

CVE-2025-24194: Apple iOS and iPadOS · Processing maliciously crafted web content may result in the disclosure of process memory

Affects Apple iOS and iPadOSSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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 31 Mar 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 2026-10-25.

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 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

1. Immediate deployment of the security updates released by Apple (iOS and iPadOS 18.4 and later) across all affected devices is critical. 2. Implement network-level protections such as web content filtering and blocking access to untrusted or suspicious websites to reduce exposure to malicious web content. 3. Educate users to avoid clicking on unknown or suspicious links, especially those received via email or messaging platforms. 4. Employ mobile device management (MDM) solutions to enforce timely patching and restrict installation of unapproved applications or content. 5. Monitor network traffic and device logs for unusual activity related to web content processing or memory access patterns. 6. Consider deploying endpoint detection and response (EDR) tools capable of detecting anomalous behaviors indicative of exploitation attempts. 7. For high-security environments, restrict or sandbox web browsing capabilities to limit potential attack surface. 8. Maintain an incident response plan that includes procedures for memory disclosure incidents and data breach containment.

Description

A logic issue was addressed with improved checks. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4. Processing maliciously crafted web content may result in the disclosure of process memory.

Impact

The primary impact of CVE-2025-24194 is the potential unauthorized disclosure of sensitive information from process memory on Apple mobile devices. For organizations worldwide, this could lead to leakage of confidential data, including credentials, personal information, or cryptographic material, which attackers could leverage for further attacks such as identity theft, espionage, or lateral movement within networks. Since the vulnerability requires user interaction (e.g., visiting a malicious website), targeted phishing or watering hole attacks could be used to exploit it. The confidentiality breach could undermine trust in mobile device security, especially in sectors handling sensitive data such as finance, healthcare, government, and critical infrastructure. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive data can have severe consequences including regulatory penalties, reputational damage, and operational disruption. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 00:45 UTC

Technical details

References

Community reviews

Related threats