CVE-2022-48503
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2022-48503 being exploited?
Yes. CVE-2022-48503 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2022-48503?
CVE-2022-48503 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-48503?
Yes. A fix has been recorded for CVE-2022-48503. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-48503 affect?
CVE-2022-48503 affects apple:safari, apple:ipados, apple:iphone_os, apple:macos, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 15.6
- affected< 12.5
- affected< 15.6
- affected< 15.6
- affected< 8.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 20 Oct 2025 (SSVC 2.0.3).
timeline
- 14 Aug 2023Published
- 20 Oct 2025Added to CISA KEV (exploited in the wild) · 797 days (about 2 years) later
- 20 Oct 2025CISA SSVC assessment: exploitation active · 1 day later
- 21 Oct 2025CVE record last updated · 1 day later
- 10 Nov 2025CISA remediation due date (US federal agencies) · 19 days later
- 2 Nov 2026Analysed by vulneraibility.com · 358 days (about 12 months) later
- Linksupport.apple.com /en-us/HT213345
- Linksupport.apple.com /en-us/HT213342
- Linksupport.apple.com /en-us/HT213341
- Linksupport.apple.com /en-us/HT213340
- Linksupport.apple.com /en-us/HT213346
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-48503
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.