Lyrie
active-exploitation
ACTIVELY EXPLOITED3 sources verified·4 min read
By Lyrie Threat Intelligence·10/20/2025

What happened

CISA added CVE-2022-48503 to the Known Exploited Vulnerabilities catalog, signaling confirmed in-the-wild exploitation requiring prioritized remediation CISA KEV. The entry covers Apple macOS, iOS, tvOS, Safari, and watchOS with an unspecified vulnerability in JavaScriptCore that, when processing web content, may allow arbitrary code execution NVD. The KEV entry indicates some impacted products may be end-of-life or end-of-service, and advises discontinuing use where mitigations are unavailable CISA KEV. The CVE record confirms the identifier and scope for Apple Multiple Products under CVE-2022-48503 MITRE CVE.

CISA’s required action is to apply vendor mitigations, follow applicable BOD 22-01 guidance for cloud services, or discontinue use if mitigations are unavailable CISA KEV. The vulnerability description aligns with remote code execution via crafted web content, as summarized by NVD for CVE-2022-48503 NVD.

Why it matters

A JavaScript engine bug that triggers during web content processing collapses the barrier between simple browsing and code execution, enabling drive‑by compromise on affected Apple platforms NVD. CISA’s placement of CVE-2022-48503 in KEV means exploitation has been observed and federal agencies are mandated to remediate on deadline, which is a strong signal for enterprise prioritization CISA KEV. The breadth of affected product lines (macOS, iOS, tvOS, Safari, watchOS) expands the attack surface across desktops, mobile devices, and embedded endpoints in Apple’s ecosystem NVD.

Because the bug is triggered by processing malicious web content, exposure exists anywhere the affected engines or frameworks handle untrusted input, increasing the likelihood of opportunistic exploitation at scale NVD. KEV inclusion also flags potential lifecycle risk: if an asset is EoL/EoS and cannot be remediated per vendor guidance, it should be removed from service to close the exposure window CISA KEV.

Technical detail

Per the CVE description, the vulnerability is unspecified within JavaScriptCore and can lead to arbitrary code execution during the handling of web content across Apple Multiple Products NVD. The CVE registration confirms Apple as the vendor and records the identifier CVE-2022-48503 for coordination and downstream tracking MITRE CVE. CISA’s KEV catalog specifically notes active exploitation and mandates remediation actions for this CVE, elevating it above routine patch advisories CISA KEV.

The lack of a disclosed root cause (“unspecified”) and the cross‑product impact means defenders should treat any JavaScriptCore execution path that parses untrusted content as potentially exploitable until vendor mitigations are applied NVD. In practical terms, that includes default browsing and any embedded web view functionality on impacted platforms listed in the KEV summary CISA KEV.

Defense

Execute CISA’s required action path: apply vendor mitigations, follow applicable BOD 22‑01 guidance for cloud services, or discontinue use if mitigations are unavailable CISA KEV. Prioritize patching or mitigations on Apple macOS, iOS, tvOS, Safari, and watchOS assets enumerated in your inventory to eliminate the web‑content RCE vector NVD. For assets that are EoL/EoS or cannot be updated within change windows, remove from service or isolate them until remediation is possible, in line with KEV guidance CISA KEV.

Treat high‑risk workflows (untrusted browsing, content preview, embedded web views) as constrained until updates are verified, given that exploitation occurs during web content processing per the CVE summary NVD. Track remediation status against CVE-2022-48503 in your vulnerability management system to ensure closure across all Apple product lines impacted by the entry MITRE CVE.

Lyrie Verdict

This is an active-exploitation, web‑content RCE in a core script engine; it moves faster than human triage can keep up CISA KEV. Lyrie’s advantage is machine‑speed suppression of this class of threat: we continuously correlate exploit‑stage signals from web‑content execution paths tied to CVE identifiers like CVE‑2022‑48503 and auto‑prioritize impacted Apple endpoints for isolation or patch enforcement without waiting for manual ticket queues NVD. Bottom line: autonomous detection and response beats drive‑by code‑execution chains that pivot off untrusted content parsing, and we tune our detectors against KEV‑listed items to cut dwell to minutes, not days CISA KEV.

Lyrie Verdict

This KEV-listed JavaScriptCore web-content RCE demands machine-speed action. Lyrie auto-correlates exploit-stage signals for CVE-2022-48503 across Apple endpoints and drives isolation/patch enforcement without human lag.