# CVE-2025-24085: Apple Multiple Products Use-After-Free

> A malicious application can exploit a use-after-free flaw to elevate privileges on Apple devices, requiring immediate patching.

- **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 29 Jan 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-7h23-57pg-3hwc

## What is CVE-2025-24085?

CVE-2025-24085 is a critical use after free vulnerability in Apple Ipados, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.6, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3, watchOS 11.3. A malicious application may be able to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 17.2.

Weakness: CWE-416 (Use After Free)

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

It affects 6 products.


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

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

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

## Is CVE-2025-24085 being exploited?

Yes. Attackers have exploited CVE-2025-24085 in the wild since at least 29 Jan 2025.

Public exploit code:

- Glass Cage is a zero-click PNG-based RCE chain in iOS 18.2.1, bypassing LockDown mode protection by exploiting ImageIO (CVE-2025-43300), then WebKit(CVE-2025-24201) and Core Media(CVE-2025-24085) to achieve sandbox escape, kernel-level access, and device bricking. Triggered via iMessage, it enables full compromise with no user interaction. (github_poc): https://github.com/JGoyd/Glass-Cage-iOS18-CVE-2025-24085-CVE-2025-24201
- macOS LaunchDaemon iOS 17.2 - Privilege Escalation (exploitdb)

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

What it is: CVE-2025-24085 is a critical use after free vulnerability in Apple Ipados, published on 27 Jan 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-24085 in the wild since at least 29 Jan 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-24085/ (Markdown: https://insights.sbomify.com/CVE-2025-24085/index.md)
```

## Sources

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

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