CVE-2025-43535VulnerabilityPublished 17 Dec 2025Updated 2 Apr 2026

CVE-2025-43535: Apple Safari · Processing maliciously crafted web content may lead to an unexpected process crash

Affects Apple SafariSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 26.2 : update Apple Safari when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 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 Safari	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-43535, organizations should promptly deploy the official patches released by Apple for Safari 26.2 and the corresponding OS updates (iOS 18.7.3, iPadOS 18.7.3, macOS Tahoe 26.2, visionOS 26.2). Beyond patching, organizations should implement web content filtering to block access to known malicious or suspicious websites that could host crafted content. Employing endpoint protection solutions capable of detecting abnormal browser crashes or memory anomalies can help identify exploitation attempts. User awareness training should emphasize caution when clicking unknown links or visiting untrusted websites. For high-security environments, consider restricting Safari usage or enforcing browser sandboxing and process isolation to limit impact from crashes. Monitoring browser crash logs and correlating with network traffic may provide early indicators of exploitation attempts. Finally, maintaining up-to-date backups and ensuring business continuity plans account for potential browser disruptions will reduce operational impact.

Description

The issue was addressed with improved memory handling. This issue is fixed in Safari 26.2, iOS 18.7.3 and iPadOS 18.7.3, iOS 26.2 and iPadOS 26.2, macOS Tahoe 26.2, visionOS 26.2. Processing maliciously crafted web content may lead to an unexpected process crash.

Impact

The primary impact of CVE-2025-43535 is denial of service through unexpected browser crashes, which can disrupt user activities and automated processes relying on Safari. Organizations with employees or customers using vulnerable Safari versions may experience reduced productivity, interrupted workflows, and potential loss of trust if service interruptions occur frequently. While the vulnerability does not compromise confidentiality or integrity, repeated crashes could be exploited in targeted denial-of-service campaigns against specific users or systems. Enterprises relying heavily on Apple ecosystems, including iOS, iPadOS, macOS Tahoe, and visionOS, may face operational challenges if patches are not applied promptly. Additionally, sectors with high dependency on web-based applications accessed via Safari, such as finance, healthcare, and government, could see increased risk of service degradation. The lack of known exploits reduces immediate risk, but the ease of triggering the crash via crafted web content means attackers could weaponize this vulnerability in phishing or watering hole attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 02:38 UTC

Technical details

References

Community reviews

Related threats