dbcve.org
IpadosOperating system · Apple

CVE-2024-40786

HIGH · 7.5 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 13.6.8 / 16.7.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
This issue was addressed through improved state management. This issue is fixed in iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Ventura 13.6.8. An attacker may be able to view sensitive user information.

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 an information disclosure vulnerability in Apple iOS, iPadOS, and macOS caused by improper state management. An attacker can exploit this to view sensitive user information on affected devices. The vulnerability affects iOS versions before 16.7.9 and 17.6, and macOS Ventura before 13.6.8.

MitigationApply the vendor-supplied patches by updating affected devices to iOS 16.7.9/17.6 or later, iPadOS 16.7.9/17.6 or later, or macOS Ventura 13.6.8 or later.

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:< 16.7.9>= 17.0, < 17.6
Iphone OsOperating system
Affected:< 16.7.9>= 17.0, < 17.6
macOSOperating system
Affected:< 13.6.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 your device type and operating system
    Determine whether the device is an iPhone (iOS), iPad (iPadOS), or Mac (macOS). On iPhone/iPad, go to Settings > General > About. On Mac, click the Apple menu and select About This Mac.
    Affected if Device runs iOS, iPadOS, or macOS Ventura
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and look at the 'Version' field. Note the full version number (e.g., 17.5, 16.7.8).
    Affected if Version is shown as less than 16.7.9, or as 17.0 through 17.5.x (anything below 17.6)
  3. Check macOS Ventura version
    On Mac, click Apple menu > About This Mac. Look at the macOS version number (e.g., 13.6, 13.5.1). Note that this vulnerability affects only macOS Ventura, not later versions like macOS Sonoma.
    Affected if macOS Ventura version is shown as less than 13.6.8 (e.g., 13.6.7, 13.5, 13.4)
  4. Compare against affected version ranges
    Use these thresholds: for iOS/iPadOS, vulnerable if version < 16.7.9 OR version is 17.0-17.5.x; for macOS Ventura, vulnerable if version < 13.6.8. If your device shows a version in these ranges, it is affected by this CVE.
    Affected if Installed version falls within any of the vulnerable ranges

A device is affected if it runs iOS or iPadOS version 16.7.8 or earlier, 17.0 through 17.5.x, or macOS Ventura 13.6.7 or earlier.

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 13.6.8 / 16.7.9 / 17.6 or later
Fixed in 13.6.816.7.917.6
Interim mitigation

Apply the vendor-supplied patches by updating affected devices to iOS 16.7.9/17.6 or later, iPadOS 16.7.9/17.6 or later, or macOS Ventura 13.6.8 or later.

Recommended fix High confidence

iOS 16.7.9, iOS 17.6, iPadOS 16.7.9, iPadOS 17.6, macOS Ventura 13.6.8

  1. Back up your device before performing any update
  2. On iPhone or iPad: Go to Settings > General > Software Update to check for and install the update
  3. For iOS 16.7.x devices: Update to iOS 16.7.9
  4. For iOS 17.0-17.5 devices: Update to iOS 17.6
  5. For iPadOS 16.7.x devices: Update to iPadOS 16.7.9
  6. For iPadOS 17.0-17.5 devices: Update to iPadOS 17.6
  7. For macOS Ventura devices: Update to macOS Ventura 13.6.8 via System Settings > Software Update
  8. After updating, verify the version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
Caveat Standard Apple minor/patch update - minimal risk; ensure backup before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40786 — 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-40786 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