Threats / Apple / CVE-2022-42827
CVE-2022-42827
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple iOS and iPadOS vulnerability
Apple iOS and iPadOS kernel contains an out-of-bounds write vulnerability allowing applications to execute code with kernel privileges.
Verdict
Today item — known-exploited.
An application can exploit improper input validation and memory bounds checking in the kernel to write beyond allocated buffers, achieving arbitrary code execution at the highest privilege level.
CISA KEV Yes · 2022-10-254EPSS 0.01136 (verify live)5CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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 2022-10-25).
Probability (EPSS)
EPSS 0.01136 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Apple, iOS and iPadOS. 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.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation, CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
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 the same day 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
I craft a malicious application that sends specially formatted input to trigger improper validation in the kernel.
Business
User devices become compromised at the kernel level, bypassing all security boundaries and isolation mechanisms.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the out-of-bounds write to overwrite kernel memory structures and inject my code into kernel execution context.
Business
Complete device compromise enables theft of sensitive data, installation of persistent malware, and loss of user privacy.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain kernel-level code execution to disable security features, modify system behavior, and persist across reboots.
Business
Enterprise deployments face elevated risk of data exfiltration, compliance violations, and inability to trust device integrity.
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