What is the Pixnapping vulnerability, and how to protect your Android smartphone? | Kaspersky official blog
The Android vulnerability CVE-2025-48561 (Pixnapping) enables the theft of any data displayed on a smartphone's screen. We explain how Pixnapping works and give advice on mitigating the risk.
AI Analysis
Technical Summary
Pixnapping is a sophisticated Android vulnerability (CVE-2025-48561) discovered by researchers that enables a malicious app to capture screen content from other apps without requiring any special permissions. The attack exploits fundamental Android functionalities: the ability to render app windows and send Intents (system calls) to other apps. The malicious app forces a target app to render sensitive information offscreen using hidden launch flags and overlays a series of translucent windows that blur and isolate individual pixels. Since the attacker app can only read pixels from its own windows, it uses a timing side-channel attack based on GPU.zip, a known vulnerability exploiting the variable time taken by GPU compression algorithms to infer pixel values. By repeating this pixel extraction process hundreds of times, the attacker reconstructs meaningful screen content such as passwords, bank balances, and one-time authentication codes. The attack was demonstrated on Android versions 13 through 16 on Google Pixel and Samsung Galaxy devices and is believed to be broadly applicable across Android devices. Google's initial patch released in September 2025 was insufficient, and a more robust fix is planned for December 2025. The GPU.zip side channel remains unpatched by GPU manufacturers. Pixnapping bypasses Android’s layered security protections including FLAG_SECURE, media projection restrictions, and app sandboxing, making it uniquely dangerous. The attack requires no user permissions beyond basic app capabilities and no user interaction, making detection and prevention challenging. Currently, no active exploitation in the wild is reported, but the potential for stealthy data theft is high. Users are advised to keep devices updated, avoid untrusted apps, and use comprehensive mobile security software.
Potential Impact
For European organizations, Pixnapping poses a significant risk of confidential data leakage from employee Android devices. Sensitive corporate information such as authentication tokens, passwords, and financial data displayed on mobile screens can be stolen silently, enabling account takeover, fraud, and unauthorized access to corporate resources. The attack’s stealth and lack of permission requirements make it difficult to detect and prevent, increasing the risk of prolonged undetected breaches. Organizations relying on Android devices for multi-factor authentication or accessing sensitive applications are particularly vulnerable. This can lead to compromised enterprise accounts, data breaches, and financial losses. The risk extends to sectors with high mobile usage such as finance, healthcare, and government. Additionally, the inability to fully patch the underlying GPU timing side channel means the threat may persist for years. The attack also undermines user trust in Android security, potentially impacting mobile workforce productivity and security policies.
Mitigation Recommendations
1. Ensure all Android devices are promptly updated with the latest security patches, especially the forthcoming December 2025 update from Google aimed at fully mitigating Pixnapping. 2. Enforce strict app installation policies restricting users to trusted app stores and vetted applications with established reputations and high user ratings. 3. Deploy enterprise mobile security solutions capable of detecting anomalous app behavior and overlay window abuses. 4. Educate employees about the risks of installing new or unknown apps and the importance of scrutinizing app permissions and behaviors. 5. Implement mobile device management (MDM) policies that limit the ability to install or run apps that can create overlay windows or send Intents to other apps. 6. Encourage use of hardware-backed multi-factor authentication methods (e.g., security keys) that do not rely solely on screen-displayed codes. 7. Monitor network traffic for unusual data exfiltration patterns that could indicate screen data theft. 8. Collaborate with device manufacturers and Google to track patch deployment and vulnerability status. 9. Consider restricting access to highly sensitive applications on Android devices until the vulnerability is fully mitigated. 10. Regularly audit and update security policies to reflect emerging mobile threats like Pixnapping.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria
What is the Pixnapping vulnerability, and how to protect your Android smartphone? | Kaspersky official blog
Description
The Android vulnerability CVE-2025-48561 (Pixnapping) enables the theft of any data displayed on a smartphone's screen. We explain how Pixnapping works and give advice on mitigating the risk.
AI-Powered Analysis
Technical Analysis
Pixnapping is a sophisticated Android vulnerability (CVE-2025-48561) discovered by researchers that enables a malicious app to capture screen content from other apps without requiring any special permissions. The attack exploits fundamental Android functionalities: the ability to render app windows and send Intents (system calls) to other apps. The malicious app forces a target app to render sensitive information offscreen using hidden launch flags and overlays a series of translucent windows that blur and isolate individual pixels. Since the attacker app can only read pixels from its own windows, it uses a timing side-channel attack based on GPU.zip, a known vulnerability exploiting the variable time taken by GPU compression algorithms to infer pixel values. By repeating this pixel extraction process hundreds of times, the attacker reconstructs meaningful screen content such as passwords, bank balances, and one-time authentication codes. The attack was demonstrated on Android versions 13 through 16 on Google Pixel and Samsung Galaxy devices and is believed to be broadly applicable across Android devices. Google's initial patch released in September 2025 was insufficient, and a more robust fix is planned for December 2025. The GPU.zip side channel remains unpatched by GPU manufacturers. Pixnapping bypasses Android’s layered security protections including FLAG_SECURE, media projection restrictions, and app sandboxing, making it uniquely dangerous. The attack requires no user permissions beyond basic app capabilities and no user interaction, making detection and prevention challenging. Currently, no active exploitation in the wild is reported, but the potential for stealthy data theft is high. Users are advised to keep devices updated, avoid untrusted apps, and use comprehensive mobile security software.
Potential Impact
For European organizations, Pixnapping poses a significant risk of confidential data leakage from employee Android devices. Sensitive corporate information such as authentication tokens, passwords, and financial data displayed on mobile screens can be stolen silently, enabling account takeover, fraud, and unauthorized access to corporate resources. The attack’s stealth and lack of permission requirements make it difficult to detect and prevent, increasing the risk of prolonged undetected breaches. Organizations relying on Android devices for multi-factor authentication or accessing sensitive applications are particularly vulnerable. This can lead to compromised enterprise accounts, data breaches, and financial losses. The risk extends to sectors with high mobile usage such as finance, healthcare, and government. Additionally, the inability to fully patch the underlying GPU timing side channel means the threat may persist for years. The attack also undermines user trust in Android security, potentially impacting mobile workforce productivity and security policies.
Mitigation Recommendations
1. Ensure all Android devices are promptly updated with the latest security patches, especially the forthcoming December 2025 update from Google aimed at fully mitigating Pixnapping. 2. Enforce strict app installation policies restricting users to trusted app stores and vetted applications with established reputations and high user ratings. 3. Deploy enterprise mobile security solutions capable of detecting anomalous app behavior and overlay window abuses. 4. Educate employees about the risks of installing new or unknown apps and the importance of scrutinizing app permissions and behaviors. 5. Implement mobile device management (MDM) policies that limit the ability to install or run apps that can create overlay windows or send Intents to other apps. 6. Encourage use of hardware-backed multi-factor authentication methods (e.g., security keys) that do not rely solely on screen-displayed codes. 7. Monitor network traffic for unusual data exfiltration patterns that could indicate screen data theft. 8. Collaborate with device manufacturers and Google to track patch deployment and vulnerability status. 9. Consider restricting access to highly sensitive applications on Android devices until the vulnerability is fully mitigated. 10. Regularly audit and update security policies to reflect emerging mobile threats like Pixnapping.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Article Source
- {"url":"https://www.kaspersky.com/blog/pixnapping-cve-2025-48561/54756/","fetched":true,"fetchedAt":"2025-11-11T16:37:05.579Z","wordCount":1845}
Threat ID: 69136631f922b639ab601387
Added to database: 11/11/2025, 4:37:05 PM
Last enriched: 11/18/2025, 9:09:34 PM
Last updated: 11/21/2025, 11:01:41 AM
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
Salesforce Instances Hacked via Gainsight Integrations
MediumCVE-2025-12964: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in nalam-1 Magical Products Display – Elementor WooCommerce Widgets | Product Sliders, Grids & AJAX Search
MediumCVE-2025-12750: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation
MediumCVE-2025-12066: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in etruel WP Delete Post Copies
MediumCVE-2025-13149: CWE-862 Missing Authorization in publishpress Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.