CVE-2024-40782
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 · uneditedA use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 17.6, iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. Processing maliciously crafted web content may lead to an unexpected process crash.
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 · moderate confidenceThis is a use-after-free vulnerability in WebKit, Apple's browser engine, affecting Safari and WebKit-based applications across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. The vulnerability is triggered when processing maliciously crafted web content, leading to an unexpected process crash due to improper memory management.
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< 17.6< 16.7.9>= 17.0, < 17.6< 16.7.9>= 17.0, < 17.6>= 14.0, < 14.6< 17.6< 1.3< 10.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple platform in useDetermine whether the system runs Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS. On macOS, check Apple menu > About This Mac. On iOS/iPadOS, go to Settings > General > About. On tvOS, go to Settings > General > About. On visionOS, go to Settings > General > About. On watchOS, go to Settings > General > About.Affected if The platform is one of Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS.
-
Check Safari version on macOS or iOSOn macOS, open Safari and go to Safari > About Safari. On iOS/iPadOS, open Settings > Safari > About. Note the version number displayed.Affected if Safari version is earlier than 17.6.
-
Check iOS or iPadOS versionOpen Settings > General > About and note the version number. Also check the build number if displayed.Affected if iOS or iPadOS version is earlier than 16.7.9, or falls between 17.0 and 17.5.x.
-
Check macOS versionOpen Apple menu > About This Mac and note the version number (such as 14.5 or 14.4).Affected if macOS version is 14.0 through 14.5.x (any version >= 14.0 but < 14.6).
-
Check tvOS, visionOS, or watchOS versionOn the device, go to Settings > General > About and note the version number displayed.Affected if tvOS is earlier than 17.6, visionOS is earlier than 1.3, or watchOS is earlier than 10.6.
A user is affected if their Safari browser version is below 17.6, their iOS/iPadOS is below 16.7.9 or between 17.0-17.5.x, their macOS is 14.0-14.5.x, or their tvOS/visionOS/watchOS is below the respective patched version.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.310.614.6
Apply the vendor-supplied patches by updating to Safari 17.6, iOS/iPadOS 16.7.9 or 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, or watchOS 10.6 as appropriate for each affected system.
Upgrade to Safari 17.6, iOS/iPadOS 16.7.9 or 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, or watchOS 10.6 depending on device
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, Apple Watch, Apple Vision Pro, or Safari browser)
- Check the current OS or Safari version on the device
- For macOS devices: upgrade to macOS Sonoma 14.6 via System Settings > Software Update
- For iPhone/iPad: upgrade to iOS/iPadOS 17.6 (or 16.7.9 for devices on iOS 16.x) via Settings > General > Software Update
- For Apple TV: upgrade to tvOS 17.6 via Settings > System > Software Updates
- For Apple Watch: upgrade to watchOS 10.6 via the Watch app on iPhone > My Watch > General > Software Update
- For Apple Vision Pro: upgrade to visionOS 1.3 via Settings > General > Software Update
- For Safari standalone: upgrade to Safari 17.6 via macOS Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- lists.debian.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-40782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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