Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Pointer Authentication Bypass in Apple RPAC

IdentifiersCVE-2025-31201CWE-693

CVE-2025-31201 is a vulnerability in Apple’s RPAC component affecting iOS, iPadOS, macOS, tvOS, and visionOS. According to Apple, an attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. Apple fixed the issue in iOS 18.4.1, iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, and visionOS 2.4.1 by removing the vulnerable code. Apple also stated it is aware of a report that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on iOS. Publicly available detail is limited; the provided material does not identify the exact vulnerable function or code path beyond RPAC and the Pointer Authentication bypass condition.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can defeat Pointer Authentication, a key exploit-mitigation mechanism on affected Apple platforms. In practical terms, this can enable an attacker who already has arbitrary memory read/write to bypass a protection intended to hinder control-flow hijacking and post-corruption exploitation. This would materially increase the reliability and capability of a broader exploit chain, facilitating deeper system compromise, including kernel-level post-exploitation or privilege-escalation objectives depending on the surrounding chain. Apple reported the issue may have been used in highly targeted real-world attacks against iOS users.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting execution of untrusted code and content, restricting installation and use of untrusted applications, and enforcing least privilege to reduce the value of post-exploitation. Use platform security controls such as application allowlisting, EDR/host-based monitoring, and review for signs of abnormal memory-manipulation or exploit-chain activity. Because this issue requires arbitrary read/write capability, mitigations that prevent initial code execution or memory-corruption exploitation are especially relevant. However, no complete vendor-provided workaround is available in the supplied content; patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Apply Apple’s security updates that address CVE-2025-31201: iOS 18.4.1, iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, and visionOS 2.4.1 or later. Apple states the fix was implemented by removing the vulnerable code. Prioritize patching exposed and high-risk devices, especially those used by likely surveillance or targeted-attack victims.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
AppleTvosoperating_system
AppleVisionosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity35

Community discussion across Reddit, Mastodon, and other social sources.