dbcve.org
IpadosOperating system · Apple

CVE-2024-27826

HIGH · 7.8 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 1.3 / 10.5 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The issue was addressed with improved memory handling. This issue is fixed in iOS 17.5 and iPadOS 17.5, macOS Monterey 12.7.6, macOS Sonoma 14.5, macOS Ventura 13.6.8, tvOS 17.5, visionOS 1.3, watchOS 10.5. A local attacker may be able to cause unexpected system shutdown.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a local privilege escalation vulnerability in multiple Apple operating systems stemming from improper memory handling. A local attacker can exploit this memory corruption issue to cause an unexpected system shutdown (denial of service). The vulnerability affects iOS, iPadOS, macOS, tvOS, visionOS, and watchOS as specified in the affected versions.

MitigationApply the vendor-supplied patches by updating all affected devices to iOS 17.5/iPadOS 17.5, macOS 12.7.6/13.6.8/14.5, tvOS 17.5, visionOS 1.3, or watchOS 10.5 respectively. Organizations should inventory Apple devices and deploy updates through their MDM or patch management infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpadosOperating system
Affected:< 17.5
Iphone OsOperating system
Affected:< 17.5
macOSOperating system
Affected:>= 12.0, < 12.7.6>= 13.0, < 13.6.8>= 14.0, < 14.5
TvosOperating system
Affected:< 17.5
VisionosOperating system
Affected:< 1.3
WatchosOperating system
Affected:< 10.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apple devices in your environment
    Inventory all Apple devices including iPhones, iPads, Mac computers, Apple TV, Apple Watch, and Apple Vision Pro. Use MDM software, network scanning, or physical inspection to compile a complete list.
    Affected if Any Apple device is present in the environment
  2. Check iOS or iPadOS version
    On the device, go to Settings > General > About > Version. Alternatively, connect to MDM or device management console to retrieve the installed iOS/iPadOS version programmatically.
    Affected if Installed version is below 17.5 on iPhone or iPad
  3. Check macOS version
    On the Mac, click the Apple menu > About This Mac. The version number appears in the window. For remote checks, use MDM tools or run 'sw_vers' in Terminal.
    Affected if Installed version is 12.0 through 12.7.5, 13.0 through 13.6.7, or 14.0 through 14.4 (any version in the affected ranges)
  4. Check tvOS version
    On Apple TV, go to Settings > General > About > Version. For remote checks, use MDM or Apple Configurator.
    Affected if Installed version is below 17.5 on Apple TV
  5. Check visionOS version
    On Apple Vision Pro, go to Settings > General > About > Version.
    Affected if Installed version is below 1.3 on Apple Vision Pro
  6. Check watchOS version
    On Apple Watch, open the Settings app on the paired iPhone, go to General > About, or check directly on Watch via Settings > General > About > Version.
    Affected if Installed version is below 10.5 on Apple Watch

A user is affected if any Apple device in their environment runs an OS version that falls within the specified vulnerable ranges for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3 / 10.5 / 12.7.6 or later
Fixed in 1.310.512.7.6
Interim mitigation

Apply the vendor-supplied patches by updating all affected devices to iOS 17.5/iPadOS 17.5, macOS 12.7.6/13.6.8/14.5, tvOS 17.5, visionOS 1.3, or watchOS 10.5 respectively. Organizations should inventory Apple devices and deploy updates through their MDM or patch management infrastructure.

Recommended fix High confidence

iOS 17.5, iPadOS 17.5, macOS Monterey 12.7.6, macOS Ventura 13.6.8, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.3, watchOS 10.5

  1. For iPhone and iPad: Go to Settings > General > Software Update and upgrade to iOS/iPadOS 17.5
  2. For Mac: Open System Settings > General > Software Update and upgrade to macOS 12.7.6 (Monterey), 13.6.8 (Ventura), or 14.5 (Sonoma) depending on your current macOS version
  3. For Apple TV: Go to Settings > General > Privacy and Security > Software Update and upgrade to tvOS 17.5
  4. For Apple Vision Pro: Go to Settings > General > Software Update and upgrade to visionOS 1.3
  5. For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and upgrade to watchOS 10.5
  6. After updating, verify the system is running the fixed version via Settings > General > About
Caveat Ensure app compatibility with the new OS versions before deploying in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27826 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data