Microsoft States New Windows Recall Bypass Is Not a Security Vulnerability
We independently review everything we recommend. When you buy through our links, we may earn a commission which is paid directly to our Australia-based writers, editors, and support staff. Thank you for your support!
Microsoft Counters Windows Recall Security Concerns
Quick Overview
- Microsoft defends the Recall feature in Windows 11 against purported security vulnerabilities.
- Researcher Alexander Hagenah showcases a newly discovered bypass technique.
- Microsoft asserts that this method functions within the security framework of Recall.
- Recall integrates robust encryption and biometric verification mechanisms.
- The security issues concern the vulnerability of the AIXHost.exe process.
- Microsoft reasserts that there is no possibility of direct access to snapshots or encryption keys.
Context of Recall’s Security Apprehensions
Recall, an AI-enhanced capability in Windows 11, allows users to locate content on their devices, including sensitive information such as screenshots and browsing history. It came under fire in 2024 when researcher Alexander Hagenah uncovered weaknesses that permitted data extraction from an unprotected database. Microsoft halted the feature’s rollout and redesigned it, reintroducing it in April 2025.
Recent Bypass Discovery
Hagenah has recently pinpointed another vulnerability in the revamped Recall, claiming it enables complete content extraction from the AI tool’s SQLite database. This bypass occurs through the AIXHost.exe process, which lacks specific security restrictions and safeguards.
Microsoft’s Reaction
Microsoft disputes the notion that the bypass represents a security flaw, claiming it conforms to Recall’s established security schema. The corporation emphasizes its architectural design, which prevents any processes external to Virtualisation-Based Security (VBS) Enclaves from directly accessing encryption keys or snapshots.
Technical Perspectives
Recall’s security improvements comprise VBS enclaves, AES-256-GCM encryption, and Windows Hello authentication. Nonetheless, the AIXHost.exe process, essential for displaying the Recall timeline, operates beyond these secure enclaves, making it vulnerable to code injections without elevated privileges.
Conclusion
Microsoft asserts that the reported bypass concerning the Windows Recall utility does not constitute a security vulnerability, as it remains within the confines of the existing security architecture. In spite of concerns raised by researcher Alexander Hagenah, Microsoft reassures users that its infrastructure effectively curtails potential data leaks.
