Sensitive screenshot exposure during iPhone Mirroring in iOS/iPadOS (UI state management)
In iOS/iPadOS, an inconsistent user interface/state management flaw in the iPhone Mirroring feature (when used with a Mac) could allow an attacker with physical access to an iPhone to take and view screenshots that contain sensitive on-screen data during an iPhone Mirroring session. Apple indicates the issue was addressed via improved state management and is fixed in iOS 26.3 and iPadOS 26.3.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Physical-access issue allowing screenshots/viewing of sensitive data during iPhone Mirroring with Mac (UIKit).
Lock-screen information disclosure due to authorization/state management issue; fixed with improved state management.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.