CVE-2024-40809
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 logic issue was addressed with improved checks. This issue is fixed in iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8, visionOS 1.3, watchOS 10.6. A shortcut may be able to bypass Internet permission requirements.
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 confidenceA logic flaw in Apple's Shortcuts application on iOS, iPadOS, macOS, visionOS, and watchOS allowed shortcuts to bypass Internet permission requirements, potentially enabling unauthorized network access without proper user consent. The vulnerability was addressed through improved permission validation checks.
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< 16.7.9>= 17.0, < 17.6< 16.7.9>= 17.0, < 17.6< 12.7.6>= 13.0, < 13.6.8>= 14.0, < 14.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device platformDetermine if the device runs iOS, iPadOS, macOS, visionOS, or watchOSAffected if Device runs any of these Apple platforms with Shortcuts app
-
Check iOS or iPadOS versionGo to Settings > General > About and note the Version number. Compare against affected ranges: < 16.7.9, >= 17.0 and < 17.6Affected if Version falls within any affected range (< 16.7.9, >= 17.0 to < 17.6)
-
Check macOS versionGo to System Settings > About (or Apple menu > About This Mac) and note the Version number. Compare against affected ranges: < 12.7.6, >= 13.0 to < 13.6.8, >= 14.0 to < 14.6Affected if Version falls within any affected range (< 12.7.6, >= 13.0 to < 13.6.8, >= 14.0 to < 14.6)
-
Check visionOS versionGo to Settings > General > About and note the Version number. Compare against affected range: < 1.3Affected if Version is less than 1.3
-
Check watchOS versionOn Apple Watch, go to Settings > General > About and note the Version number. Compare against affected range: < 10.6Affected if Version is less than 10.6
Your device is affected if it runs the Shortcuts app on any platform with an OS version matching the affected ranges listed above.
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.612.7.6
Apply the appropriate Apple security update for the affected platform: iOS 16.7.9/17.6, iPadOS 16.7.9/17.6, macOS Monterey 12.7.6/Ventura 13.6.8/Sonoma 14.6, visionOS 1.3, or watchOS 10.6.
iOS 16.7.9 or iOS 17.6 / iPadOS 16.7.9 or iPadOS 17.6 / macOS 12.7.6, 13.6.8, or 14.6 / visionOS 1.3 / watchOS 10.6 (depending on your device)
- For iPhone users: Go to Settings > General > Software Update and install iOS 16.7.9 or iOS 17.6 depending on your device compatibility
- For iPad users: Go to Settings > General > Software Update and install iPadOS 16.7.9 or iPadOS 17.6 depending on your device compatibility
- For Mac users: Go to System Settings > General > Software Update and install the appropriate update: macOS Monterey 12.7.6, macOS Ventura 13.6.8, or macOS Sonoma 14.6
- For Apple Watch users: Go to Settings > General > Software Update on your watch or through the Watch app on iPhone to install watchOS 10.6
- For Vision Pro users: Go to Settings > General > Software Update and install visionOS 1.3
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40809 — 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
- 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-40809 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