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

CVE-2025-46316: Processing a maliciously crafted Pages document may result

Affects Apple PagesSource CVE Database V5

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

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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-26.

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 Pages to 15.1; iOS and iPadOS and macOS to 26.1.

Affected software

Product	Affected	Fixed in
ApplePages	Affected <15.1	Fixed in 15.1
AppleiOS and iPadOS	Affected <26.1	Fixed in 26.1
ApplemacOS	Affected <26.1	Fixed in 26.1

AI-suggested

To mitigate CVE-2025-46316, organizations and users should promptly update Apple Pages to version 15.1 or later on macOS Tahoe 26.1, iOS 26.1, and iPadOS 26.1 or newer. Ensure that all Apple devices are running the latest OS versions that include the patched Pages application. Implement strict email and document filtering policies to block or quarantine suspicious or unsolicited Pages documents from unknown or untrusted sources. Educate users about the risks of opening documents from unverified senders to reduce the likelihood of social engineering exploitation. Employ endpoint protection solutions capable of detecting anomalous application crashes or memory disclosures. Where feasible, restrict the use of Pages documents in high-risk environments or use sandboxing technologies to limit the impact of potential crashes or memory leaks. Regularly audit and monitor logs for unusual application behavior or crashes related to Pages. Finally, maintain an incident response plan that includes procedures for handling suspected exploitation of document parsing vulnerabilities.

Description

An out-of-bounds read was addressed with improved input validation. This issue is fixed in Pages 15.1, iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1. Processing a maliciously crafted Pages document may result in unexpected termination or disclosure of process memory.

Impact

The primary impact of CVE-2025-46316 is on application availability and potential information disclosure. When a user opens a maliciously crafted Pages document, the application may crash unexpectedly, disrupting productivity and potentially causing data loss if unsaved work is lost. More critically, the out-of-bounds read can disclose portions of process memory, which might contain sensitive information such as document contents, user data, or other in-memory secrets. Although the vulnerability does not allow direct code execution or privilege escalation, the information leakage could aid attackers in further attacks or reconnaissance. Organizations relying heavily on Apple Pages for document creation and editing, especially in environments handling sensitive or confidential information, face risks of data exposure and operational disruption. Since exploitation requires user interaction (opening a malicious document), phishing or social engineering campaigns could be used to deliver the payload. The lack of known exploits in the wild reduces immediate risk, but the medium severity score and potential for information leakage warrant timely mitigation. Enterprises with Apple device fleets should prioritize patching to maintain operational stability and data confidentiality.

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:45 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats