Threats / Apple / CVE-2025-31201
CVE-2025-31201
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple Multiple Products vulnerability
Apple products contain an arbitrary read and write vulnerability enabling Pointer Authentication bypass, allowing attackers to access and modify protected memory regions.
Verdict
Today item — known-exploited.
This vulnerability permits memory corruption attacks that circumvent Apple's pointer integrity protections. Active exploitation in the wild indicates immediate risk to users of affected Apple platforms across iOS, iPadOS, and macOS.
CISA KEV Yes · 2025-04-174EPSS 0.14652 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-17).
Probability (EPSS)
EPSS 0.14652 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit the arbitrary read capability to leak pointer values and defeat ASLR protections.
Business
User devices lose memory layout confidentiality, enabling targeted code execution attacks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use arbitrary write access to corrupt authenticated pointers and bypass Pointer Authentication Code validation.
Business
Core security mechanism designed to prevent control flow hijacking is neutralized.
3
Lateral reach — past segmentation narrative 3
Attacker
I chain the pointer corruption with memory writes to redirect execution to attacker-controlled code.
Business
Attackers gain arbitrary code execution within privileged processes or kernel context.
4
Data at risk — exfiltration narrative 4
Attacker
I escalate privileges or escape sandbox restrictions using kernel-level code execution.
Business
Complete device compromise occurs, enabling data theft, malware installation, and persistent access.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05