CVE-2025-46306
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 · uneditedThe issue was addressed with improved bounds checks. This issue is fixed in Keynote 15.1, iOS 26 and iPadOS 26, macOS Tahoe 26. Processing a maliciously crafted Keynote file may disclose memory contents.
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 memory disclosure vulnerability in Apple Keynote, iOS, iPadOS, and macOS allows processing of maliciously crafted Keynote files to expose memory contents due to missing bounds checks during file parsing.
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< 15.1< 26.0< 26.0< 26.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Keynote version on macOSOpen Keynote app, select Keynote menu > About Keynote, or right-click Keynote in Applications > Get Info. Note the version number under 'Version:'Affected if Version number is less than 15.1 (e.g., 15.0.x or earlier)
-
Check macOS versionClick Apple menu > System Settings > About, or use command: sw_vers. Note the macOS version (e.g., 25.x, 24.x, etc.)Affected if macOS version is less than 26.0 (any version below 26.0, such as 25.x, 24.x, 23.x, etc.)
-
Check iOS version on iPhoneOpen Settings > General > About. Note the iOS version displayed next to 'Version'Affected if iOS version is less than 26.0 (any version below 26.0, such as 18.x, 17.x, etc.)
-
Check iPadOS version on iPadOpen Settings > General > About. Note the iPadOS version displayed next to 'Version'Affected if iPadOS version is less than 26.0 (any version below 26.0, such as 18.x, 17.x, etc.)
You are affected if Keynote is below 15.1 OR your iOS/iPadOS/macOS is below 26.0, since the vulnerability can be triggered by opening a maliciously crafted Keynote file in any of these unpatched versions.
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 · scoped15.126.0
Apply the vendor-provided updates: Keynote 15.1, iOS 26, iPadOS 26, or macOS Tahoe 26. Until patched, avoid opening Keynote files from untrusted sources.
Keynote 15.1, iOS 26, iPadOS 26, macOS Tahoe 26
- Check current version of Keynote, iOS, iPadOS, or macOS
- For Keynote: Open App Store, navigate to Updates, and update to version 15.1
- For iOS/iPadOS: Go to Settings > General > Software Update and update to iOS/iPadOS 26
- For macOS: Go to System Settings > General > Software Update and update to macOS Tahoe 26
- After updating, verify the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46306 — 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-46306 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