· 32 CVEs

watchOS 11.2 Security Update

watchOS 11.2 fixes 32 vulnerabilities. Every fix, in Apple's words, with what it could have allowed.

What watchOS 11.2 Fixes

watchOS 11.2, released December 11, 2024, fixes 32 vulnerabilities in 19 parts of the system, according to Apple's security advisory.

Apple does not say that any of them were exploited before the fix. That makes watchOS 11.2 a routine security update: worth installing soon, not an emergency.

It has since been superseded: the newest security release for watchOS 11 is watchOS 11.6, from July 29, 2025, which includes these fixes.

What an attacker could doFixes
Run code2
Elevated privileges or sandbox escape4
Private data or protections bypassed7
Crash or denial of service14
Other5

Grouped by us from the impact Apple gives for each fix; the impact lines below are Apple's own.

Which Devices Get watchOS 11.2

Apple lists watchOS 11.2 for: Apple Watch Series 6 and later.

How to Install watchOS 11.2

Open the Watch app on the paired iPhone, then General → Software Update. The watch needs to be on its charger and within range of the iPhone.

Security fixes are cumulative: any later release for the same version includes these as well, so if you are already past watchOS 11.2 there is nothing to do.

Every Fix in watchOS 11.2

All 32 CVEs in Apple's advisory, the most serious kinds first. Each entry is the part of the system affected, Apple's description of the impact and the fix, and the CVE ID.

  • ImageIO

    Processing a maliciously crafted image may lead to arbitrary code execution

    A use-after-free issue was addressed with improved memory management.

    CVE-2024-54499

  • libexpat

    A remote attacker may cause an unexpected app termination or arbitrary code execution

    This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.

    CVE-2024-45490

  • Apple Account

    An attacker in a privileged network position may be able to track a user's activity

    The issue was addressed with improved handling of protocols.

    CVE-2024-40864

  • Kernel

    An app may be able to break out of its sandbox

    The issue was addressed with improved checks.

    CVE-2024-54468

  • libxpc

    An app may be able to break out of its sandbox

    The issue was addressed with improved checks.

    CVE-2024-54514

  • libxpc

    An app may be able to gain elevated privileges

    A logic issue was addressed with improved checks.

    CVE-2024-44225

  • APFS

    An app may be able to access user-sensitive data

    This issue was addressed through improved state management.

    CVE-2024-54541

  • AppleMobileFileIntegrity

    A malicious app may be able to access private information

    The issue was addressed with improved checks.

    CVE-2024-54526

  • AppleMobileFileIntegrity

    An app may be able to access sensitive user data

    This issue was addressed with improved checks.

    CVE-2024-54527

  • Crash Reporter

    An app may be able to access sensitive user data

    A permissions issue was addressed with additional restrictions.

    CVE-2024-54513

  • Kernel

    An app may be able to leak sensitive kernel state

    A race condition was addressed with improved locking.

    CVE-2024-54510

  • Passkeys

    Password autofill may fill in passwords after failing authentication

    The issue was addressed with improved checks.

    CVE-2024-54530

  • Safari Private Browsing

    Private Browsing tabs may be accessed without authentication

    An authentication issue was addressed with improved state management.

    CVE-2024-54542

  • ICU

    Processing maliciously crafted web content may lead to an unexpected process crash

    An out-of-bounds access issue was addressed with improved bounds checking.

    CVE-2024-54478

  • IOMobileFrameBuffer

    An app may be able to corrupt coprocessor memory

    The issue was addressed with improved bounds checks.

    CVE-2024-54517 CVE-2024-54518 CVE-2024-54522 CVE-2024-54523

  • QuartzCore

    Processing web content may lead to a denial-of-service

    The issue was addressed with improved checks.

    CVE-2024-54497

  • SceneKit

    Processing a maliciously crafted file may lead to a denial of service

    The issue was addressed with improved checks.

    CVE-2024-54501

  • Vim

    Processing a maliciously crafted file may lead to heap corruption

    This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org .

    CVE-2024-45306

  • WebKit

    Processing maliciously crafted web content may lead to an unexpected process crash

    The issue was addressed with improved checks.

    CVE-2024-54479 CVE-2024-54502

  • WebKit

    Processing maliciously crafted web content may lead to an unexpected process crash

    The issue was addressed with improved memory handling.

    CVE-2024-54508

  • WebKit

    Processing maliciously crafted web content may lead to memory corruption

    A type confusion issue was addressed with improved memory handling.

    CVE-2024-54505

  • WebKit

    Processing maliciously crafted web content may lead to memory corruption

    The issue was addressed with improved memory handling.

    CVE-2024-54534 CVE-2024-54543

  • Face Gallery

    A system binary could be used to fingerprint a user's Apple Account

    The issue was addressed by removing the relevant flags.

    CVE-2024-54512

  • FontParser

    Processing a maliciously crafted font may result in the disclosure of process memory

    The issue was addressed with improved checks.

    CVE-2024-54486

  • ImageIO

    Processing a maliciously crafted image may result in disclosure of process memory

    The issue was addressed with improved checks.

    CVE-2024-54500

  • Kernel

    An attacker may be able to create a read-only memory mapping that can be written to

    A race condition was addressed with additional validation.

    CVE-2024-54494

  • MobileBackup

    Restoring a maliciously crafted backup file may lead to modification of protected system files

    A logic issue was addressed with improved file handling.

    CVE-2024-54525

watchOS 11 Security Release History

watchOS 11.2 in context: the security releases Apple has published for watchOS 11, newest first, with the number of fixes each carried.

ReleaseReleasedFixes
watchOS 11.6July 29, 202523
watchOS 11.5May 12, 202526 Exploited
watchOS 11.4April 1, 202551 Exploited
watchOS 11.3.1February 10, 20251 Exploited
watchOS 11.3January 27, 202520
watchOS 11.2December 11, 202432
watchOS 11.1October 28, 202423
watchOS 11September 16, 202416

The Same Fixes Elsewhere

Apple ships most fixes to every platform that shares the code, and to older versions still under support. These releases close at least one of the same CVEs:

Frequently Asked Questions

What does watchOS 11.2 fix?

32 security vulnerabilities in 19 parts of the system, from Apple's advisory of December 11, 2024. 2 could have let an attacker run code.

Was anything fixed in watchOS 11.2 exploited?

Apple does not say so for any of the 32 fixes.

Which devices can install watchOS 11.2?

Apple Watch Series 6 and later.

Is watchOS 11.2 the latest security update?

No. watchOS 11.6, from July 29, 2025, is newer and includes these fixes.

Source: About the security content of watchOS 11.2, Apple. Rechecked automatically while Apple is still adding entries.

Every Apple security update