CVE-2025-43342: 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 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apple Safari | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-43342, organizations and users should promptly update all affected Apple devices to the patched versions: Safari 26, iOS 18.7, iPadOS 18.7, macOS Tahoe 26, tvOS 26, visionOS 26, and watchOS 26. Beyond patching, network defenses should be enhanced to detect and block malicious web content targeting Safari browsers, including deploying web filtering and intrusion prevention systems with updated signatures. Security teams should monitor web traffic for unusual patterns or spikes in Safari crashes that could indicate exploitation attempts. Employing endpoint detection and response (EDR) solutions capable of identifying abnormal process terminations or memory corruption events can aid in early detection. Organizations should also educate users about the risks of visiting untrusted websites and encourage safe browsing practices. For high-risk environments, consider restricting Safari usage or implementing browser isolation technologies until patches are fully deployed. Regular vulnerability scanning and asset inventory management will help ensure all Apple devices are identified and updated promptly. Finally, maintain up-to-date backups and incident response plans to minimize impact in case of successful exploitation.
Description
A correctness issue was addressed with improved checks. This issue is fixed in Safari 26, iOS 18.7 and iPadOS 18.7, iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. Processing maliciously crafted web content may lead to an unexpected process crash.
References
- support.apple.com/en-us/125108 (opens in a new tab)
- support.apple.com/en-us/125109 (opens in a new tab)
- support.apple.com/en-us/125110 (opens in a new tab)
- support.apple.com/en-us/125113 (opens in a new tab)
- support.apple.com/en-us/125114 (opens in a new tab)
- support.apple.com/en-us/125115 (opens in a new tab)
- support.apple.com/en-us/125116 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/57 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/53 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/59 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/49 (opens in a new tab)
- openwall.com/lists/oss-security/2025/09/22/3 (opens in a new tab)