VulnerabilityPublished 24 Aug 2022Updated 30 May 2025

CVE-2022-32793: Apple macOS · Out-of-bounds Write

Affects Apple macOSSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 12.5 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 12.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Aug 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apple macOS to 12.5.

Affected software

Product	Affected	Fixed in
Apple macOS	Affected <12.5	Fixed in 12.5

AI-suggested

European organizations should prioritize updating all Apple devices to the latest OS versions that include the patch for CVE-2022-32793: macOS Monterey 12.5, watchOS 8.7, tvOS 15.6, iOS 15.6, and iPadOS 15.6 or later. Beyond patching, organizations should implement strict application whitelisting and endpoint protection to prevent untrusted or malicious apps from executing. Employing Mobile Device Management (MDM) solutions can help enforce update policies and monitor device compliance. Network segmentation and limiting exposure of Apple devices to untrusted networks can reduce attack surface. Regular security audits and memory integrity monitoring can help detect anomalous behavior indicative of exploitation attempts. Since the vulnerability allows kernel memory disclosure without authentication, restricting installation of apps to trusted sources (e.g., Apple App Store) is critical. Finally, organizations should educate users about the importance of timely updates and the risks of installing unverified software.

Description

Multiple out-of-bounds write issues were addressed with improved bounds checking. This issue is fixed in macOS Monterey 12.5, watchOS 8.7, tvOS 15.6, iOS 15.6 and iPadOS 15.6. An app may be able to disclose kernel memory.

Impact

For European organizations, this vulnerability poses a significant risk especially for enterprises and government agencies that rely on Apple devices for sensitive operations. Disclosure of kernel memory could lead to leakage of confidential information, including cryptographic material or system internals, which could be leveraged for further attacks such as privilege escalation or persistent compromise. Since the vulnerability requires no privileges or user interaction, it could be exploited by malicious apps or malware delivered through various vectors, including supply chain attacks or malicious downloads. Organizations in sectors such as finance, healthcare, critical infrastructure, and government are particularly at risk due to the sensitivity of their data and the widespread use of Apple devices. The impact extends to privacy concerns under GDPR if personal data is exposed. Additionally, the lack of known exploits in the wild suggests that timely patching can effectively mitigate the risk before active exploitation occurs.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 14:43 UTC

WeaknessesCWE-787

Technical details

References

Community reviews

Related threats