CVE-2025-43436
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 permissions issue was addressed with additional restrictions. This issue is fixed in iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. 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 · moderate confidenceThis is an information disclosure vulnerability in Apple's operating systems where a malicious application could bypass permissions restrictions to enumerate all apps installed on a user's device. The vulnerability allowed apps to access a list of installed applications, potentially revealing sensitive information about user interests, professional activities, or personal habits. The fix involved adding additional restrictions to prevent unauthorized access to app inventory information.
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< 26.1< 26.1< 26.1< 26.1< 26.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS/iPadOS version on iPhone or iPadOn the device, go to Settings > General > About and read the Version fieldAffected if Version number is less than 26.1 (for example, 26.0, 25.x, or earlier)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TVAffected if Version number is less than 26.1
-
Check visionOS version on Apple VisionGo to Settings > General > About > Version on the Vision deviceAffected if Version number is less than 26.1
-
Check watchOS version on Apple WatchOn the paired iPhone, open the Watch app, go to General > About, or on the Watch go to Settings > General > AboutAffected if Version number is less than 26.1
If any Apple device runs an operating system version earlier than 26.1, it is affected by this information disclosure vulnerability that allows unauthorized app enumeration.
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 · scoped26.1
Organizations should ensure all affected Apple devices (iOS/iPadOS, macOS, tvOS, visionOS, watchOS) are updated to version 26.1 or later. Mobile device management (MDM) solutions can be used to verify compliance and force updates across the fleet.
iOS 26.1, iPadOS 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1
- Upgrade iPhone to iOS 26.1 or later
- Upgrade iPad to iPadOS 26.1 or later
- Upgrade Apple TV to tvOS 26.1 or later
- Upgrade Apple Vision Pro to visionOS 26.1 or later
- Upgrade Apple Watch to watchOS 26.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43436 — 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-43436 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