# CVE-2023-41064: Apple iOS, iPadOS, and macOS ImageIO Buffer Overflow

> Attackers can execute arbitrary code by tricking users into opening a malicious image on Apple devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 11 Sep 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2023
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-8c6q-gxj3-w77f

## What is CVE-2023-41064?

CVE-2023-41064 is a high-severity memory corruption vulnerability in Apple Ipados, published on 7 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A buffer overflow issue was addressed with improved memory handling. This issue is fixed in iOS 16.6.1 and iPadOS 16.6.1, macOS Monterey 12.6.9, macOS Ventura 13.5.2, iOS 15.7.9 and iPadOS 15.7.9, macOS Big Sur 11.7.10. Processing a maliciously crafted image may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-41064?

It affects 3 products.


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

## How do I fix CVE-2023-41064?

No fix has been published for CVE-2023-41064 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Oct 2023.

## Is CVE-2023-41064 being exploited?

Yes. Attackers have exploited CVE-2023-41064 in the wild since at least 11 Sep 2023.

Public exploit code:

- https://github.com/MrR0b0t19/CVE-2023-41064 (github_poc): https://github.com/MrR0b0t19/CVE-2023-41064
- longitudes de código para desencadenar esta vulnerabilidad (github_poc): https://github.com/MrR0b0t19/vulnerabilidad-LibWebP-CVE-2023-41064
- https://github.com/K4Der11000/k4_cve-2023-41064 (github_poc): https://github.com/K4Der11000/k4_cve-2023-41064

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41064 and fix it if it is affected.

What it is: CVE-2023-41064 is a high-severity memory corruption vulnerability in Apple Ipados, published on 7 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2023-41064 in the wild since at least 11 Sep 2023.

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-2023-41064/ (Markdown: https://insights.sbomify.com/CVE-2023-41064/index.md)
```

## Sources

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

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