Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2022-48503

Apple Multiple Products Unspecified Vulnerability

Apple Multiple Products

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.

CVSS
8.8
HIGH
EPSS
3.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
14 Aug 2023
CWE-129

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 20 October 2025. US federal agencies were required to remediate it by 10 November 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 3.2%, which is higher than 88.3% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2022-48503 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-48503.

What does CVE-2022-48503 affect?

CVE-2022-48503 affects Apple Multiple Products. 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.

How severe is CVE-2022-48503?

CVE-2022-48503 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 3.2%, higher than 88.3% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 November 2025.

How should organisations respond to CVE-2022-48503?

Apply the vendor patch for Apple Multiple Products as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.