CVE-2025-43361
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 · uneditedAn out-of-bounds read was addressed with improved bounds checking. This issue is fixed in iOS 26 and iPadOS 26, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. A malicious app may be able to read kernel memory.
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 confidenceAn out-of-bounds read vulnerability in Apple's kernel allows a maliciously crafted application to read kernel memory due to insufficient bounds checking. This constitutes a memory disclosure vulnerability that could expose sensitive kernel data.
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< 14.8.2>= 15.0, < 15.7.2< 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
- 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 the device type and current OS versionOn iPhone/iPad: Settings > General > About > Software Version. On Mac: Apple menu > About This Mac > macOS version. On Apple TV: Settings > General > About > Version. On Apple Watch: Settings > General > About > Watch OS. On Vision Pro: Settings > General > About > visionOS.Affected if The device runs an affected OS version (iOS/iPadOS < 26.1, macOS < 14.8.2 or >= 15.0 and < 15.7.2, tvOS < 26.1, watchOS < 26.1, visionOS < 26.1)
-
Confirm the vulnerability applies to your deviceThis is a kernel-level vulnerability present in all Apple devices running the affected OS versions. The flaw is triggered by a maliciously crafted application.Affected if The device runs a kernel version matching the affected OS ranges listed above
-
Verify if third-party app installation is allowedOn iPhone/iPad: Settings > VPN & Device Management (or General > Device Management). On Mac: System Settings > Privacy & Security > Security. Check if 'Allow apps downloaded from: App Store' is the only setting enabled.Affected if This check helps determine exposure vector; devices with App Store-only restrictions have lower attack surface, but the vulnerability still exists in the kernel regardless of app source restrictions
You are affected if your Apple device runs any OS version lower than 26.1 for iOS/iPadOS/tvOS/watchOS/visionOS, or lower than 14.8.2 / between 15.0-15.7.2 for macOS.
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 · scoped14.8.215.7.226.1
Update all affected Apple devices to iOS 26, iPadOS 26, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26. As a defense-in-depth measure, restrict app installations to the App Store only until patches are applied.
iOS 26.1+, iPadOS 26.1+, macOS Sonoma 14.8.2+, macOS Sequoia 15.7.2+, macOS Tahoe 26+, tvOS 26+, visionOS 26+, watchOS 26+
- Back up your device data before upgrading
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 26.1 or later / iPadOS 26.1 or later
- For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.8.2 or later, or macOS Sequoia 15.7.2 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 26 or later
- For Apple Watch: Go to Settings > General > Software Update and install watchOS 26 or later
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26 or later
- Verify the update was successful by checking the software version after updating
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-43361 — 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-43361 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