# CVE-2022-48618: Apple Multiple Products Memory Corruption

> An attacker with arbitrary read and write capabilities can bypass Pointer Authentication on Apple operating systems.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 31 Jan 2024 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-v2rr-hhf4-8739

## What is CVE-2022-48618?

CVE-2022-48618 is a high-severity vulnerability in Apple Ipados, published on 9 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The issue was addressed with improved checks. This issue is fixed in macOS Ventura 13.1, watchOS 9.2, iOS 16.2 and iPadOS 16.2, tvOS 16.2. An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. Apple is aware of a report that this issue may have been exploited against versions of iOS released before iOS 15.7.1.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2022-48618?

It affects 5 products.


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

## How do I fix CVE-2022-48618?

No fix has been published for CVE-2022-48618 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Feb 2024.

## Is CVE-2022-48618 being exploited?

Yes. Attackers have exploited CVE-2022-48618 in the wild since at least 31 Jan 2024.

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

What it is: CVE-2022-48618 is a high-severity vulnerability in Apple Ipados, published on 9 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-48618 in the wild since at least 31 Jan 2024.

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

## Sources

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

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