IRONSMITHINTEL
MEDIUMCVSS5.5
|
Actively Exploited
|CISA KEV|CVE-2020-27950|Auth: none — unauthenticated|Reboot: required|Manual only

Apple Multiple Products Memory Initialization Vulnerability (CVE-2020-27950)

Apple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability that may allow a malicious application to disclose kernel memory.

Published Dec 8, 2020 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, without authentication, can achieve full data confidentiality loss. Federal agencies are required to remediate by 2022-05-03 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-665) (CWE-665) vulnerability in Apple Multiple Products. A memory initialization issue was addressed. This issue is fixed in macOS Big Sur 11.0.1, watchOS 7.1, iOS 12.4.9, watchOS 6.2.9, Security Update 2020-006 High Sierra, Security Update 2020-006 Mojave, iOS 14.2 and iPadOS 14.2, watchOS 5.3.9, macOS Catalina 10.15.7 Supplemental Update, macOS Catalina 10.15.7 Update. A malicious application may be able to disclose kernel memory. Exploitation requires local access, low attack complexity, no authentication required, and 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 < 14.2; iphone os: v < 12.4.9, 14.0 ≤ v < 14.2; macos: v < 10.15.7, 11.0 ≤ v < 11.0.1; watchos: v < 5.3.9, 6.0 ≤ v < 6.2.9, 7.0 ≤ v < 7.1
Real-world incidentsWhat we've seen

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

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2020-27950'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.