# CVE-2025-43300: Apple iOS, iPadOS, and macOS Out-of-Bounds Write

> Processing a malicious image file can cause memory corruption, potentially allowing code execution in Apple operating systems.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 21 Aug 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-cpwx-wfp4-x368

## What is CVE-2025-43300?

CVE-2025-43300 is a critical memory corruption vulnerability in Apple Ipados, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-43300?

It affects 3 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos.

## How do I fix CVE-2025-43300?

No fix has been published for CVE-2025-43300 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 11 Sep 2025.

## Is CVE-2025-43300 being exploited?

Yes. Attackers have exploited CVE-2025-43300 in the wild since at least 21 Aug 2025.

Public exploit code:

- This is POC for IOS 0click CVE-2025-43300 (github_poc): https://github.com/hunters-sec/CVE-2025-43300
- CVE-2025-43300: iOS/macOS DNG Image Processing Memory Corruption (github_poc): https://github.com/PwnToday/CVE-2025-43300
- https://github.com/ticofookfook/CVE-2025-43300 (github_poc): https://github.com/ticofookfook/CVE-2025-43300
- This is POC for IOS 0click CVE-2025-43300 (github_poc): https://github.com/Dark-life944/CVE-2025
- https://github.com/veniversum/cve-2025-43300 (github_poc): https://github.com/veniversum/cve-2025-43300

## Other vulnerabilities in Apple Ipados

- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)
- [CVE-2022-22587](https://insights.sbomify.com/CVE-2022-22587/): Apple Memory Corruption (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43300 and fix it if it is affected.

What it is: CVE-2025-43300 is a critical memory corruption vulnerability in Apple Ipados, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-43300 in the wild since at least 21 Aug 2025.

Affected product: Apple Ipados. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43300/ (Markdown: https://insights.sbomify.com/CVE-2025-43300/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43300
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43300
- OSV: https://osv.dev/vulnerability/CVE-2025-43300

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43300/
Summaries are generated and may contain mistakes; the official description above is the record.