IRONSMITHINTEL
HIGHCVSS7.8
|
Actively Exploited
|CISA KEV|CVE-2022-32917|Auth: low — authenticated user|Reboot: required|Manual only

Apple iOS, iPadOS, and macOS Remote Code Execution Vulnerability (CVE-2022-32917)

Apple kernel, which is included in iOS, iPadOS, and macOS, contains an unspecified vulnerability where an application may be able to execute code with kernel privileges.

Published Sep 20, 2022 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, with a low-privilege account, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2022-10-05 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Out-of-bounds Write (CWE-787) vulnerability in Apple iOS, iPadOS, and macOS. The issue was addressed with improved bounds checks. This issue is fixed in macOS Monterey 12.6, iOS 15.7 and iPadOS 15.7, iOS 16, macOS Big Sur 11.7. An application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited.. Exploitation requires local access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●Apple Device Administrators
●Endpoint Security
●IT Security
●Running ipados: v < 15.7; iphone os: v < 15.7; macos: 11.0 ≤ v < 11.7, 12.0.0 ≤ v < 12.6
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2022-09-14 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2022-10-05.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for os installs in scope.
2
Apply the vendor security update referenced in CVE-2022-32917's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2022-32917↗ MSRC Advisory↗ NVD↗ Vendor Advisory