· 26 CVEs

watchOS 11.5 Security Update

watchOS 11.5 fixes 26 vulnerabilities, and Apple says one may have been exploited. Every fix, in Apple's words, with what it could have allowed.

Actively exploited — update now

What watchOS 11.5 Fixes

watchOS 11.5, released May 12, 2025, fixes 26 vulnerabilities in 13 parts of the system, according to Apple's security advisory.

Apple says one of these flaws — CVE-2025-31200 — may already have been exploited. That makes watchOS 11.5 an update to install now rather than at the weekend.

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 escape3
Private data or protections bypassed2
Spoofing1
Crash or denial of service16
Other2

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

Exploited Before the Fix

Apple flags a fix as possibly exploited when it has a credible report that the flaw was used against real people before the patch. This one is the reason to update today.

  • CoreAudio Exploited

    Processing an audio stream in a maliciously crafted media file may result in code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS released before iOS 18.4.1.

    A memory corruption issue was addressed with improved bounds checking.

    CVE-2025-31200

Which Devices Get watchOS 11.5

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

How to Install watchOS 11.5

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.5 there is nothing to do.

Every Fix in watchOS 11.5

The rest of Apple's advisory — every fix not already listed above, 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.

  • libexpat

    Multiple issues in libexpat, including 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-8176

  • Kernel

    An attacker may be able to cause unexpected system termination or corrupt kernel memory

    The issue was addressed with improved memory handling.

    CVE-2025-31219

  • mDNSResponder

    A user may be able to elevate privileges

    A correctness issue was addressed with improved checks.

    CVE-2025-31222

  • Wi-Fi

    An attacker in physical proximity may be able to cause an out-of-bounds read in kernel memory

    An out-of-bounds read was addressed with improved bounds checking.

    CVE-2025-43374

  • Core Bluetooth

    An app may be able to access sensitive user data

    This issue was addressed through improved state management.

    CVE-2025-31212

  • StoreKit

    An app may be able to access sensitive user data

    A privacy issue was addressed with improved private data redaction for log entries.

    CVE-2025-31242

  • WebKit

    A malicious website may exfiltrate data cross-origin

    The issue was addressed with improved checks.

    CVE-2025-31205

  • AppleJPEG

    Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory

    The issue was addressed with improved input sanitization.

    CVE-2025-31251

  • CoreAudio

    Parsing a file may lead to an unexpected app termination

    The issue was addressed with improved checks.

    CVE-2025-31208

  • CoreMedia

    Parsing a file may lead to an unexpected app termination

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

    CVE-2025-31239

  • CoreMedia

    Processing a maliciously crafted video file may lead to unexpected app termination or corrupt process memory

    The issue was addressed with improved input sanitization.

    CVE-2025-31233

  • ImageIO

    Processing a maliciously crafted image may lead to a denial-of-service

    A logic issue was addressed with improved checks.

    CVE-2025-31226

  • Kernel

    A remote attacker may be able to cause unexpected system termination

    The issue was addressed with improved checks.

    CVE-2025-24224

  • Kernel

    A remote attacker may cause an unexpected app termination

    A double free issue was addressed with improved memory management.

    CVE-2025-31241

  • WebKit

    A type confusion issue could lead to memory corruption

    This issue was addressed with improved handling of floats.

    CVE-2025-24213

  • WebKit

    Processing maliciously crafted web content may lead to memory corruption

    The issue was addressed with improved checks.

    CVE-2025-31223 CVE-2025-31238

  • WebKit

    Processing maliciously crafted web content may lead to memory corruption

    The issue was addressed with improved memory handling.

    CVE-2025-24223 CVE-2025-31204

  • WebKit

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

    The issue was addressed with improved input validation.

    CVE-2025-31217

  • WebKit

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

    The issue was addressed with improved checks.

    CVE-2025-31215

  • WebKit

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

    A type confusion issue was addressed with improved state handling.

    CVE-2025-31206

  • WebKit

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

    This issue was addressed with improved memory handling.

    CVE-2025-31257

  • CoreGraphics

    Parsing a file may lead to disclosure of user information

    An out-of-bounds read was addressed with improved bounds checking.

    CVE-2025-31209

  • Security

    A remote attacker may be able to leak memory

    An integer overflow was addressed with improved input validation.

    CVE-2025-31221

watchOS 11 Security Release History

watchOS 11.5 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

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.5 fix?

26 security vulnerabilities in 13 parts of the system, from Apple's advisory of May 12, 2025. 2 could have let an attacker run code.

Was anything fixed in watchOS 11.5 exploited?

Yes. Apple says CVE-2025-31200 may have been exploited before the fix. Install it now.

Which devices can install watchOS 11.5?

Apple Watch Series 6 and later.

Is watchOS 11.5 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.5, Apple. Rechecked automatically while Apple is still adding entries.

Every Apple security update