# CVE-2022-48503: Apple Multiple Products Unspecified

> Attackers can execute arbitrary code by tricking users into visiting malicious web content in Safari or other Apple browsers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 Oct 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Aug 2023
- **Updated:** 21 Oct 2025
- **Also known as:** DEBIAN-CVE-2022-48503, GHSA-hqf2-wqhm-8v23, UBUNTU-CVE-2022-48503

## What is CVE-2022-48503?

CVE-2022-48503 is a high-severity memory corruption vulnerability in Apple Ipados, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The issue was addressed with improved bounds checks. This issue is fixed in tvOS 15.6, watchOS 8.7, iOS 15.6 and iPadOS 15.6, macOS Monterey 12.5, Safari 15.6. Processing web content may lead to arbitrary code execution.

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 6 products.


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

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

Upgrade to a fixed version. US federal agencies must fix it by 10 Nov 2025.

## Is CVE-2022-48503 being exploited?

Yes. Attackers have exploited CVE-2022-48503 in the wild since at least 20 Oct 2025.

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

What it is: CVE-2022-48503 is a high-severity memory corruption vulnerability in Apple Ipados, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2022-48503 in the wild since at least 20 Oct 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-2022-48503/ (Markdown: https://insights.sbomify.com/CVE-2022-48503/index.md)
```

## Sources

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

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