CVE-2025-30426
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 · uneditedThis issue was addressed with additional entitlement checks. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4. An app may be able to enumerate a user's installed apps.
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 confidenceA vulnerability in Apple's mobile and desktop operating systems allowed a malicious application to enumerate all installed apps on a user's device through improper entitlement validation, exposing sensitive user profile information without authorization.
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.7.6>= 18.0, < 18.4< 18.4>= 15.0, < 15.4< 18.4< 2.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check iOS or iPadOS version on iPhone/iPadOpen Settings > General > About, and note the version number displayed next to 'Version'Affected if the version is below 17.7.6, or is 18.0 through 18.3 (anything less than 18.4)
-
Check macOS version on MacClick the Apple menu > About This Mac, or open System Settings > About, and note the version number under macOSAffected if the version is 15.0, 15.1, 15.2, or 15.3 (anything from 15.0 up to but not including 15.4)
-
Check tvOS version on Apple TVOpen Settings > General > About > Version, and note the displayed version numberAffected if the version is below 18.4 (any version from the initial 18.0 release up to 18.3)
-
Check visionOS version on Apple Vision ProOpen Settings > General > About, and note the version number shown for visionOSAffected if the version is below 2.4
You are affected if your device runs an unpatched iOS/iPadOS, macOS, tvOS, or visionOS version within 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 · scoped2.415.417.7.6
Update to the fixed versions: iOS 18.4, iPadOS 18.4/17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, or watchOS 11.4.
iOS 18.4 / iPadOS 18.4 / iPadOS 17.7.6 / macOS Sequoia 15.4 / tvOS 18.4 / visionOS 2.4
- Identify the affected device type (iPhone, iPad, Mac, Apple TV, or Apple Vision Pro)
- For iPhone/iPad: Upgrade to iOS/iPadOS 18.4, or for devices on iPadOS 17.x, upgrade to 17.7.6
- For Mac: Upgrade to macOS Sequoia 15.4
- For Apple TV: Upgrade to tvOS 18.4
- For Apple Vision Pro: Upgrade to visionOS 2.4
- Verify the update by going to Settings > General > Software Update (iOS/iPadOS/tvOS/visionOS) or System Settings > General > Software Update (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30426 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30426 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