# CVE-2025-24111: Memory corruption in iOS and iPadOS

> An app can cause unexpected system termination due to a memory corruption issue in Apple operating systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-gc4x-2qcw-h9vv

## What is CVE-2025-24111?

CVE-2025-24111 is a medium-severity memory corruption vulnerability in Apple Ipados, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.7, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3, watchOS 11.3. An app may be able to cause unexpected system termination.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 6 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Tvos, Apple Visionos, Apple Watchos.

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

No fix has been published for CVE-2025-24111 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24111 being exploited?

There is no known exploitation of CVE-2025-24111 in the wild and no public exploit code.

## 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-2025-24111 and fix it if it is affected.

What it is: CVE-2025-24111 is a medium-severity memory corruption vulnerability in Apple Ipados, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24111 in the wild and no public exploit code.

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

## Sources

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

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