IRONSMITHINTEL
CRITICALCVSS10.0
|
Actively Exploited
|CISA KEV|CVE-2025-43300|Auth: none — unauthenticated|Reboot: required|Manual only

Apple iOS, iPadOS, and macOS Out-of-Bounds Write Vulnerability (CVE-2025-43300)

Apple iOS, iPadOS, and macOS contain an out-of-bounds write vulnerability in the Image I/O framework.

Published Aug 21, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-09-11 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Out-of-bounds Write (CWE-787) vulnerability in Apple iOS, iPadOS, and macOS. An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.8.5 and iPadOS 15.8.5, iOS 16.7.12 and iPadOS 16.7.12, iOS 18.6.2 and iPadOS 18.6.2, iPadOS 17.7.10, macOS Sequoia 15.6.1, macOS Sonoma 14.7.8, macOS Ventura 13.7.8. Processing a malicious image file may result in memory corruption. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

Apple Device Administrators
Endpoint Security
IT Security
Running ipados: v < 15.8.5, 16.0 ≤ v < 16.7.12, 17.0 ≤ v < 17.7.10, 18.0 ≤ v < 18.6.2; iphone os: v < 15.8.5, 16.0 ≤ v < 16.7.12, 17.0 ≤ v < 18.6.2; macos: 13.0 ≤ v < 13.7.8, 14.0 ≤ v < 14.7.8, 15.0 ≤ v < 15.6.1
Real-world incidentsWhat we've seen

Active exploitation documented in the wild. Threat-research write-up: https://github.com/b1n4r1b01/n-days/blob/main/CVE-2025-43300.md

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for os installs in scope.
2
Apply the vendor security update referenced in CVE-2025-43300's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.