# CVE-2024-27818: Memory corruption in iOS and iPadOS

> An attacker can cause unexpected app termination or arbitrary code execution via improved memory handling flaws in Apple operating systems.

- **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:** Not known
- **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:** 13 May 2024
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-3xmr-5wwh-fr8m

## What is CVE-2024-27818?

CVE-2024-27818 is a high-severity memory corruption vulnerability in Apple Ipados, published on 13 May 2024. 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

The issue was addressed with improved memory handling. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5. An attacker may be able to cause unexpected app termination or arbitrary code execution.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-27818?

It affects 3 products.


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

## How do I fix CVE-2024-27818?

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

## Is CVE-2024-27818 being exploited?

There is no known exploitation of CVE-2024-27818 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-2024-27818 and fix it if it is affected.

What it is: CVE-2024-27818 is a high-severity memory corruption vulnerability in Apple Ipados, published on 13 May 2024. 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: There is no known exploitation of CVE-2024-27818 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-2024-27818/ (Markdown: https://insights.sbomify.com/CVE-2024-27818/index.md)
```

## Sources

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

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