CVE-2025-43300

Description

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.

CVSS v3.1 Score

10.0

CRITICAL

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

CISA Known Exploited Vulnerability

This vulnerability is actively exploited in the wild.

Added: Aug 21, 2025 Remediation due: Sep 11, 2025

Weakness Type (CWE)

CWE-787 Out-of-bounds Write

Affected Products

Vendor	Product	Versions
apple	ipados	< 15.8.5
apple	ipados	16.0 — 16.7.12
apple	ipados	17.0 — 17.7.10
apple	ipados	18.0 — 18.6.2
apple	iphone_os	< 15.8.5
apple	iphone_os	16.0 — 16.7.12
apple	iphone_os	17.0 — 18.6.2
apple	macos	13.0 — 13.7.8
apple	macos	14.0 — 14.7.8
apple	macos	15.0 — 15.6.1

References

Advisories & Patches

https://support.apple.com/en-us/124925 https://support.apple.com/en-us/124926 https://support.apple.com/en-us/124927 https://support.apple.com/en-us/124928 https://support.apple.com/en-us/124929 https://support.apple.com/en-us/125141 https://support.apple.com/en-us/125142

Exploits

https://github.com/b1n4r1b01/n-days/blob/main/CVE-2025-43300.md

Other References

http://seclists.org/fulldisclosure/2025/Sep/10 http://seclists.org/fulldisclosure/2025/Sep/14 http://seclists.org/fulldisclosure/2025/Sep/52 https://github.com/cisagov/vulnrichment/issues/201 https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-43300

Frequently Asked Questions

What is CVE-2025-43300? +

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. It has a CVSS v3.1 base score of 10.0 (CRITICAL). This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild.

How severe is CVE-2025-43300? +

CVE-2025-43300 has a CVSS v3.1 score of 10.0 out of 10, rated CRITICAL. This is a critical vulnerability that should be patched immediately.

What products are affected by CVE-2025-43300? +

CVE-2025-43300 affects products from apple, specifically: ipados, iphone_os, macos. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2025-43300? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-3298

The method "sock_recvfrom_into()" of "asyncio.ProacterEventLoop" (Windows only) was missing a boundary check for the data buffer when using nbytes parameter. …

CVE-2026-40489

editorconfig-core-c is an EditorConfig core library for use by plugins supporting EditorConfig parsing. Versions up to and including 0.12.10 have …

CVE-2025-3154

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by an invalid VerticesPerRow value in a PDF shading dictionary.

CVE-2025-4640

Out-of-bounds Write vulnerability in PointCloudLibrary pcl allows Overflow Buffers. Since version 1.14.0, PCL by default uses a zlib installation from …

CVE-2025-5688

We have identified a buffer overflow issue allowing out-of-bounds write when processing LLMNR or mDNS queries with very long DNS …

CVE-2025-49848

An Out-of-bounds Write vulnerability exists within the parsing of PRJ files. The issues result from the lack of proper validation …