# CVE-2022-32839: Memory corruption in macOS

> A remote attacker can trigger memory corruption to cause application termination or execute arbitrary code on Apple devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2022
- **Updated:** 29 May 2025
- **Also known as:** GHSA-26rv-q89r-636r

## What is CVE-2022-32839?

CVE-2022-32839 is a critical memory corruption vulnerability in Apple Ipados, published on 24 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The issue was addressed with improved bounds checks. This issue is fixed in macOS Monterey 12.5, macOS Big Sur 11.6.8, Security Update 2022-005 Catalina, iOS 15.6 and iPadOS 15.6, tvOS 15.6, watchOS 8.7. A remote user may cause an unexpected app termination or arbitrary code execution.

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

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

It affects 6 products.


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

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

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

## Is CVE-2022-32839 being exploited?

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

What it is: CVE-2022-32839 is a critical memory corruption vulnerability in Apple Ipados, published on 24 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32839 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-2022-32839/ (Markdown: https://insights.sbomify.com/CVE-2022-32839/index.md)
```

## Sources

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

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