CVE-2025-46306VulnerabilityPublished 28 Jan 2026Updated 2 Apr 2026

CVE-2025-46306: Processing a maliciously crafted Keynote file may disclose memory contents

Affects Apple KeynoteSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 15.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.1, 26

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Keynote to 15.1; iOS and iPadOS and macOS to 26.

Affected software

Product	Affected	Fixed in
AppleKeynote	Affected <15.1	Fixed in 15.1
AppleiOS and iPadOS	Affected <26	Fixed in 26
ApplemacOS	Affected <26	Fixed in 26

AI-suggested

To mitigate CVE-2025-46306, organizations should: 1) Immediately update Apple Keynote to version 15.1 or later and ensure that iOS 26, iPadOS 26, and macOS Tahoe 26 are deployed on all relevant devices. 2) Implement strict email and file filtering to detect and block suspicious or unsolicited Keynote files, especially from unknown sources. 3) Educate users about the risks of opening files from untrusted or unexpected senders, emphasizing caution with Keynote files. 4) Employ endpoint protection solutions capable of detecting anomalous file parsing behavior or memory disclosure attempts. 5) Monitor network and endpoint logs for unusual activity related to Keynote file handling. 6) Consider restricting the use of Keynote files in sensitive environments or sandboxing the application to limit potential data exposure. These steps go beyond generic patching by focusing on user awareness, detection, and containment strategies.

Description

The 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.

Impact

The primary impact of CVE-2025-46306 is the potential disclosure of sensitive memory contents, which can compromise confidentiality. For organizations, this could mean leakage of sensitive corporate information, intellectual property, or user credentials if malicious Keynote files are opened by employees. Since the vulnerability requires user interaction, targeted phishing campaigns or malicious file distribution could be used to exploit this flaw. Although the vulnerability does not affect integrity or availability, the exposure of confidential data can lead to further attacks, such as identity theft, espionage, or unauthorized access to other systems. Organizations relying heavily on Apple Keynote for presentations and document sharing, especially in sectors like finance, government, and technology, may face increased risk. The medium severity rating suggests that while the threat is significant, it is not as critical as remote code execution vulnerabilities, but still warrants timely remediation to prevent data leaks.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 02:44 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats