CVE-2025-43347: Apple iOS and iPadOS · An input validation issue was addressed
Affects Apple iOS and iPadOSSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% 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 iOS and iPadOS | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-43347 effectively, organizations should: 1) Immediately update all Apple devices to iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, and watchOS 26 or later, as these versions contain the fix that removes the vulnerable code. 2) Implement network segmentation to limit exposure of Apple devices to untrusted networks, reducing the attack surface. 3) Deploy intrusion detection and prevention systems (IDPS) with updated signatures to detect anomalous input patterns that could indicate exploitation attempts. 4) Enforce strict device management policies using Mobile Device Management (MDM) solutions to ensure timely patch deployment and compliance monitoring. 5) Educate users and administrators about the critical nature of this vulnerability and the importance of applying updates promptly. 6) Monitor security advisories and threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability. 7) Conduct regular security assessments and penetration testing focusing on Apple device environments to identify residual risks. These steps go beyond generic patching advice by emphasizing proactive network controls, monitoring, and user awareness tailored to the Apple ecosystem.
Description
This issue was addressed by removing the vulnerable code. This issue is fixed in iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. An input validation issue was addressed.
References
- support.apple.com/en-us/125108 (opens in a new tab)
- support.apple.com/en-us/125110 (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/56 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/53 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/58 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Sep/49 (opens in a new tab)