Threats / Apple / CVE-2022-48503
CVE-2022-48503
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple Multiple Products vulnerability
Apple JavaScriptCore vulnerability in macOS, iOS, tvOS, Safari, and watchOS allows arbitrary code execution through malicious web content processing.
Verdict
Today item — known-exploited.
A remote code execution flaw in JavaScriptCore affects multiple Apple platforms. Exploitation occurs passively when users visit compromised or attacker-controlled websites. The vulnerability has been observed in active exploitation.
CISA KEV Yes · 2025-10-204EPSS 0.03213 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-20).
Probability (EPSS)
EPSS 0.03213 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 798 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Craft malicious web content designed to trigger the JavaScriptCore parsing vulnerability.
Business
User devices become compromised without user awareness, enabling data theft, surveillance, or lateral movement within enterprise networks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Host the malicious content on a website or inject it into legitimate web traffic to reach target users.
Business
Attack surface spans all users accessing web content across Apple's ecosystem, creating widespread exposure for consumer and enterprise deployments.
3
Lateral reach — past segmentation narrative 3
Attacker
Execute arbitrary code with the privileges of the affected application or user session.
Business
Attackers gain persistent access to sensitive data, system resources, and can establish footholds for advanced persistent threats.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05