# Android Security Published articles for Android Security. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Google's September 2026 Pixel update addresses a modem vulnerability reportedly under limited, targeted exploitation DevFeed: [Google's September 2026 Pixel update addresses a modem vulnerability reportedly under limited, targeted exploitation]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-16T10:39:04Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Google](), [pixel](), [Vulnerabilities](), [Android Security](), [Security & Privacy](), [Mobile]() Tags: [android-security](), [bugs](), [cve-2026-58704](), [google](), [mobile](), [modem](), [news](), [pixel](), [security](), [update](), [vulnerabilities](), [vulnerability]() ### AI overview Google's September 2026 Pixel security update fixes 110 vulnerabilities, including CVE-2026-58704, a high-severity cellular modem permission-bypass flaw that may be under limited, targeted exploitation. Pixel users should install the update and verify that their device shows the September 5, 2026 security patch level or later. ### Source excerpt Google's September Pixel update fixes 110 vulnerabilities, including a modem flaw being used in limited, targeted attacks. ## How Android Strongbox and Open Standards Enable the Future of High-Assurance Digital Credentials DevFeed: [How Android Strongbox and Open Standards Enable the Future of High-Assurance Digital Credentials]() Original publisher: [Read original article]() Author: Jason Wong Published: 2026-09-01T12:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Hardware](), [Architecture & Design](), [cross-platform]() Tags: [android](), [android-security](), [compliance](), [cross-platform](), [cryptographic](), [hardware](), [identity](), [none](), [open](), [security]() ### AI overview Android Strongbox uses tamper-resistant hardware, key attestation, and remote key provisioning to support high-assurance digital credentials based on open, cross-platform standards. ### Source excerpt Checking phone to see image of digital credential ## 4 new ways Android is protecting your network connections DevFeed: [4 new ways Android is protecting your network connections]() Original publisher: [Read original article]() Author: Shuaibo Huang Published: 2026-08-27T14:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Android](), [Network](), [Security](), [networking](), [App]() Tags: [android](), [android-security](), [apps](), [developers](), [devices](), [dns](), [gaming](), [github](), [network](), [networking](), [none](), [privacy](), [security]() ### AI overview Android 17 introduces network security protections including Encrypted Client Hello support with private DNS to hide visited domain names, plus Local Network Protection requiring permission for apps to scan or connect to devices on a home Wi-Fi network. The article also outlines developer steps involving OkHttp 5.5.0, ECH, and HTTPS resource record query optimization. ### Source excerpt Android bot with a shield protecting the network ## AAOS SDV - Secure by Design DevFeed: [AAOS SDV - Secure by Design]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-24T16:00:31Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Security](), [virtualization](), [virtual machines](), [SELinux](), [POSIX](), [Processes](), [Google]() Tags: [android](), [android-security](), [article](), [google](), [posix](), [process](), [security](), [selinux](), [virtual-machines](), [virtualization]() ### AI overview This article explains the security design of Android Automotive Operating System for Software Defined Vehicle (AAOS SDV). It describes virtualization for domain isolation, UID-based application and service sandboxing, POSIX capabilities, SELinux deny-by-default enforcement, and Android's vulnerability management and disclosure processes. ### Source excerpt Posted by Markus Vill, Software Engineer, Sean Keys, Security Engineer, and Istvan Nador, Software Engineer, Android Auto At Google, we believe our products should be secure by design, which is why we built the Android Automotive Operating System for Software Defined Vehicle (AAOS SDV) on existing, market-proven platforms, leveraging virtualization technologies like Cuttlefish. While our release announcements focused on the features, this blog post outlines some of the security concepts. Foundation: Domain IsolationVirtualization to isolate co-hosted instances The current trend of consolidating Electronic Control Units (ECUs) into a single chip reduces isolation by running multiple domains side-by-side. While AAOS SDV instances provide internal isolation mechanisms, it is often preferable to run logical domains independently. For instance, a cluster and an infotainment system have distinct requirements. We use virtual machines to run multiple instances in parallel, ensuring that sharing remains explicit and isolation is the default behavior. Inherited Android Security AAOS SDV evolved from Microdroid, a minimalistic Android version optimized for privacy virtual machines (pVM). This lineage provides Android platform engineers with established security features they already know. Process Isolation & Deny by Default AAOS SDV follows Android's User ID (UID)-based isolation model to set up a sandbox for each application. Each service runs in a dedicated process with a unique UID to manage access rights, data directories, and other restrictions. We employ Portable Operating System Interface (POSIX) capabilities to strictly limit operations and pair this with Security-Enhanced Linux (SELinux) to enforce a "deny-by-default" posture. This approach restricts each service to the absolute minimum required, meaning missing configurations block access rather than creating an over-permissive system. We apply this same strategy to our communication permission system, as explained l ## AAOS SDV - Secure by Design DevFeed: [AAOS SDV - Secure by Design]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-24T16:00:31Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Android](), [Security](), [SELinux](), [virtualization](), [vulnerability management](), [Process](), [Resilience](), [Google]() Tags: [android](), [android-security](), [article](), [automotive](), [blog](), [deep-dive](), [google](), [process](), [resilience](), [security](), [selinux](), [virtualization](), [vulnerabilities](), [vulnerability-management]() ### AI overview AAOS SDV is presented as a secure-by-design platform for software-defined vehicles. The article explains how virtualization isolates co-hosted domains, while Android UID-based process sandboxes, POSIX capabilities, and SELinux enforce least privilege and deny-by-default access. It also describes vulnerability response, penetration testing, security audits, and architectural reviews. ### Source excerpt Posted by Markus Vill, Software Engineer, Sean Keys, Security Engineer, and Istvan Nador, Software Engineer, Android Auto At Google, we believe our products should be secure by design, which is why we built the Android Automotive Operating System for Software Defined Vehicle (AAOS SDV) on existing, market-proven platforms, leveraging virtualization technologies like Cuttlefish. While our release announcements focused on the features, this blog post outlines some of the security concepts. Foundation: Domain IsolationVirtualization to isolate co-hosted instances The current trend of consolidating Electronic Control Units (ECUs) into a single chip reduces isolation by running multiple domains side-by-side. While AAOS SDV instances provide internal isolation mechanisms, it is often preferable to run logical domains independently. For instance, a cluster and an infotainment system have distinct requirements. We use virtual machines to run multiple instances in parallel, ensuring that sharing remains explicit and isolation is the default behavior. Inherited Android Security AAOS SDV evolved from Microdroid, a minimalistic Android version optimized for privacy virtual machines (pVM). This lineage provides Android platform engineers with established security features they already know. Process Isolation & Deny by Default AAOS SDV follows Android's User ID (UID)-based isolation model to set up a sandbox for each application. Each service runs in a dedicated process with a unique UID to manage access rights, data directories, and other restrictions. We employ Portable Operating System Interface (POSIX) capabilities to strictly limit operations and pair this with Security-Enhanced Linux (SELinux) to enforce a "deny-by-default" posture. This approach restricts each service to the absolute minimum required, meaning missing configurations block access rather than creating an over-permissive system. We apply this same strategy to our communication permission system, as explained l ## Balancing Interoperability and Security in the Age of AI DevFeed: [Balancing Interoperability and Security in the Age of AI]() Original publisher: [Read original article]() Author: Eugene Liderman Published: 2026-08-05T01:00:00Z Content type: opinion Language: en Sources: [Security]() Topics: [AI Bots](), [AI Chat]() Tags: [ai](), [ai-agents](), [android](), [android-security](), [chatgpt](), [claude](), [interoperability](), [none](), [privacy](), [sandboxes](), [security]() ### AI overview The article argues that proposed EU interoperability measures for Android AI services could require user-downloaded AI agents to receive deep system access, weakening Android's security model. It calls for safeguards and cybersecurity consultation during implementation. ### Source excerpt Over the last six months, we have been engaging closely with the European Commission (EC) after they opened specification proceedings related to Android interoperability... ## How Android helps keep you safe from impersonation scams with fake call detection DevFeed: [How Android helps keep you safe from impersonation scams with fake call detection]() Original publisher: [Read original article]() Author: Oren Schetrit Published: 2026-06-02T18:00:00Z Content type: release Language: en Sources: [Security]() Topics: [spoofing]() Tags: [ai](), [android](), [android-security](), [attacks](), [audio](), [fraud](), [mobile-security](), [none](), [scams](), [spoof](), [voice](), [voice-cloning]() ### AI overview Android introduces fake call detection to flag suspected spoofed calls between contacts using Phone by Google, aiming to counter AI voice-cloning impersonation scams. ### Source excerpt Warning that says 'someone may be pretending to call from your contact's number' ## What's New in Android Security and Privacy in 2026 DevFeed: [What's New in Android Security and Privacy in 2026]() Original publisher: [Read original article]() Author: Eugene Liderman Published: 2026-05-12T17:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Android](), [Android Security](), [Security](), [spoofing](), [Social engineering](), [threat detection](), [On-device AI](), [Chrome]() Tags: [ai](), [android](), [android-security](), [fraud](), [none](), [on-device-ai](), [security](), [social-engineering](), [spoofing](), [threat-detection]() ### AI overview The article describes planned Android security and privacy enhancements for 2026, including verified financial calls to combat spoofed banking scams. Android can verify incoming calls through participating financial apps and automatically end calls that are not genuine. It also highlights expanded Live Threat Detection, which uses on-device AI to analyze app behavior and warn about suspicious activity. ### Source excerpt New Android security and privacy features ## Android's Agentic Future: Building Gemini Intelligence on a Foundation of Security & Privacy DevFeed: [Android's Agentic Future: Building Gemini Intelligence on a Foundation of Security & Privacy]() Original publisher: [Read original article]() Author: Dave Kleidermacher Published: 2026-05-12T15:00:00Z Content type: article Language: en Sources: [Security]() Topics: [AI Chat]() Tags: [agentic](), [ai](), [android](), [android-security](), [app](), [applications](), [apps](), [architecture](), [automation](), [cloud](), [compute](), [data](), [feature](), [features](), [gemini](), [google](), [none](), [privacy](), [security]() ### AI overview The article outlines security and privacy principles for Gemini Intelligence on Android, emphasizing user control, data protection, and transparency for AI-assisted and proactive features. ### Source excerpt Gemini Intelligence security and privacy principles ## Evolving Verifiable Trust: Bringing Binary Transparency to the Android Ecosystem DevFeed: [Evolving Verifiable Trust: Bringing Binary Transparency to the Android Ecosystem]() Original publisher: [Read original article]() Author: Kevin Chao Published: 2026-05-04T16:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Android](), [Google](), [Operating system](), [Software]() Tags: [android](), [android-security](), [applications](), [architecture](), [attacks](), [cryptographic](), [google](), [none](), [os](), [production](), [supply-chain]() ### AI overview Google describes expanding binary transparency across the Android ecosystem. Public, append-only ledgers will provide cryptographic records for production Google applications and Mainline OS modules, allowing users to verify that installed software was authorized and has not been modified. ### Source excerpt A diagram of the architecture of accountability ## Bringing Rust to the Pixel Baseband DevFeed: [Bringing Rust to the Pixel Baseband]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-04-10T15:12:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Rust](), [Memory Safety](), [Security](), [Parsing](), [Google]() Tags: [android](), [android-security](), [dns](), [google](), [internet](), [library](), [memory-safety](), [none](), [open-source](), [parsing](), [pixel](), [remote-code-execution](), [rust](), [security](), [test-coverage](), [vulnerabilities]() ### AI overview Google describes integrating a memory-safe Rust DNS parser into Pixel modem firmware. The post explains the security motivation, the modem's remote attack surface, and the evaluation of open-source Rust DNS libraries, identifying hickory-proto as the best candidate based on maintenance, test coverage, and adoption. ### Source excerpt Posted by Jiacheng Lu, Software Engineer, Google Pixel Team Google is continuously advancing the security of Pixel devices. We have been focusing on hardening the cellular baseband modem against exploitation. Recognizing the risks associated within the complex modem firmware, Pixel 9 shipped with mitigations against a range of memory-safety vulnerabilities. For Pixel 10, Google is advancing its proactive security measures further. Following our previous discussion on "Deploying Rust in Existing Firmware Codebases", this post shares a concrete application: integrating a memory-safe Rust DNS(Domain Name System) parser into the modem firmware. The new Rust-based DNS parser significantly reduces our security risk by mitigating an entire class of vulnerabilities in a risky area, while also laying the foundation for broader adoption of memory-safe code in other areas. Here we share our experience of working on it, and hope it can inspire the use of more memory safe languages in low-level environments. Why Modem Memory Safety Can't Wait In recent years, we have seen increasing interest in the cellular modem from attackers and security researchers. For example, Google's Project Zero gained remote code execution on Pixel modems over the Internet. Pixel modem has tens of Megabytes of executable code. Given the complexity and remote attack surface of the modem, other critical memory safety vulnerabilities may remain in the predominantly memory-unsafe firmware code. Why DNS? The DNS protocol is most commonly known in the context of browsers finding websites. With the evolution of cellular technology, modern cellular communications have migrated to digital data networks; consequently, even basic operations such as call forwarding rely on DNS services. DNS is a complex protocol and requires parsing of untrusted data, which can lead to vulnerabilities, particularly when implemented in a memory-unsafe language (example: CVE-2024-27227). Implementing the DNS parser in Rust offers va ## Bringing Rust to the Pixel Baseband DevFeed: [Bringing Rust to the Pixel Baseband]() Original publisher: [Read original article]() Author: Jiacheng Lu Published: 2026-04-10T09:56:00Z Content type: article Language: en Sources: [Security]() Topics: [Vulnerabilities]() Tags: [android-security](), [devices](), [dns](), [google](), [memory-safety](), [none](), [open-source](), [rust](), [security](), [test-coverage](), [vulnerabilities]() ### AI overview Google describes integrating a memory-safe Rust DNS parser into Pixel 10 modem firmware to reduce risks from memory-safety vulnerabilities. ### Source excerpt Google is continuously advancing the security of Pixel devices. ## Security for the Quantum Era: Implementing Post-Quantum Cryptography in Android DevFeed: [Security for the Quantum Era: Implementing Post-Quantum Cryptography in Android]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-03-25T13:00:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Post-quantum cryptography](), [Post Quantum Cryptography (PQC)](), [Android](), [Security](), [Architecture & Design](), [Google]() Tags: [android](), [android-security](), [cryptography](), [google](), [none](), [os](), [post-quantum](), [post-quantum-cryptography](), [post-quantum-cryptography-pqc](), [security](), [upgrade]() ### AI overview Google describes Android's plan to test post-quantum cryptography enhancements in the next Android 17 beta and make them generally available in the Android 17 production release. The upgrade integrates finalized NIST post-quantum cryptography standards into the operating system's architecture and chain of trust. ### Source excerpt Posted by Eric Lynch, Product Manager, Android and Dom Elliott, Group Product Manager, Google Play Modern digital security is at a turning point. We are on the threshold of using quantum computers to solve "impossible" problems in drug discovery, materials science, and energy--tasks that even the most powerful classical supercomputers cannot handle. However, the same unique ability to consider different options simultaneously also allows these machines to bypass our current digital locks. This puts the public-key cryptography we've relied on for decades at risk, potentially compromising everything from bank transfers to trade secrets. To secure our future, it is vital to adopt the new Post-Quantum Cryptography (PQC) standards National Institute of Standards and Technology (NIST) is urging before large-scale, fault-tolerant quantum computers become a reality. To stay ahead of the curve, the technology industry must undertake a proactive, multi-year migration to Post-Quantum Cryptography (PQC). We have been preparing for a post-quantum world since 2016, conducting pioneering experiments with post-quantum cryptography, rolling out post-quantum capabilities in our products, and sharing our expertise through threat models and technical papers. For Android, the objective extends beyond patching individual applications or transport protocols. The imperative is to ensure that the entire platform architecture is resilient for the decades to come. We are beginning tests of PQC enhancements starting in the next Android 17 beta, followed by general availability in the Android 17 production release. This deployment introduces a comprehensive architectural upgrade that is being rolled out across the operating system. By integrating the recently finalized NIST PQC standards deep into the platform, we're establishing a new, quantum-resistant chain of trust. This chain of trust secures the platform continuously--from the moment the OS powers on, to the execution of applications distri ## Android expands AI-powered scam detection to Samsung devices and more regions DevFeed: [Android expands AI-powered scam detection to Samsung devices and more regions]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-02-25T15:17:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Android](), [Google AI](), [Google](), [Mobile]() Tags: [ai](), [android](), [android-security](), [devices](), [google](), [mobile](), [none](), [on-device-ai](), [protection](), [scams](), [smartphones]() ### AI overview Google describes Android's AI-powered scam protections, including Scam Detection warnings for suspicious calls. The article announces expansion of call Scam Detection to Samsung devices and additional regions, while noting existing availability on Google Pixel devices in several countries. ### Source excerpt Posted by Lyubov Farafonova, Product Manager, Phone by Google; Alberto Pastor Nieto, Sr. Product Manager Google Messages and RCS Spam and Abuse We've shared how Android's proactive, multi-layered scam defenses utilize Google AI to protect users around the world from over 10 billion suspected malicious calls and messages every month1. While that scale is significant, the true impact of these protections is best understood through the stories of the individuals they help keep safe every day. This includes people like Majik B., an IT professional in Sunnyvale, California. Despite his technical background, Majik recently found himself on a call that felt dangerously legitimate. While using his Pixel, he received a call that appeared to be from his bank. The number looked correct, the caller knew his name and his address, and the story about a "suspicious charge" made perfect sense. "I'm usually pretty careful about this stuff," Majik recalled, "but I stayed on the line longer than I normally would. Even knowing how these scams work, it was convincing in the moment." The turning point came when his phone displayed a Scam Detection warning during the call, which provided a critical moment to pause and reflect. Majik hung up, checked his bank app directly, and confirmed there was no fraudulent charge. For Majik, Scam Detection was the intervention he needed: "The warning is what made me pause and avoid a bad situation". While stories like Majik's show how our existing protections provide a robust shield against scams, our work isn't done. As scammers evolve their tactics and create more convincing and personalized threats, we're using the best of Google AI to stay one step ahead. A recent evaluation by Counterpoint Research found that Android smartphones provide the most comprehensive AI-powered protections of any mobile platform. We are committed to building on this foundation by expanding our AI-powered protections to more users and devices, while rolling out new feature ## Keeping Google Play & Android app ecosystems safe in 2025 DevFeed: [Keeping Google Play & Android app ecosystems safe in 2025]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-02-19T17:00:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Google Play](), [Google](), [Android](), [Artificial Intelligence](), [Malware](), [data]() Tags: [2025](), [ai](), [android](), [android-security](), [app-ecosystem](), [data](), [google](), [google-play](), [google-play-protect](), [malware](), [none](), [safety]() ### AI overview Google describes its 2025 efforts to protect the Google Play and Android app ecosystems, including preventing more than 1.75 million policy-violating apps from being published, banning over 80,000 harmful developer accounts, and expanding AI-assisted detection and privacy protections. ### Source excerpt Posted by Vijaya Kaza, VP and GM, App & Ecosystem Trust The Android ecosystem is a thriving global community built on trust, giving billions of users the confidence to download the latest apps. In order to maintain that trust, we're focused on ensuring that apps do not cause real-world harm, such as malware, financial fraud, hidden subscriptions, and privacy invasions. As bad actors leverage AI to change their tactics and launch increasingly sophisticated attacks, we've deepened our investments in AI and real-time defenses over the last year to maintain the upper hand and stop these threats before they reach users. Upgrading Google Play's AI-powered, multi-layered user protections We've seen a clear impact from these safety efforts on Google Play. In 2025, we prevented over 1.75 million policy-violating apps from being published on Google Play and banned more than 80,000 bad developer accounts that attempted to publish harmful apps. These figures demonstrate how our proactive protections and push for a more accountable ecosystem are discouraging bad actors from publishing malicious apps, while our new tools help honest developers build compliant apps more easily. Initiatives like developer verification, mandatory pre-review checks, and testing requirements have raised the bar for the Google Play ecosystem, significantly reducing the paths for bad actors to enter. User safety is at the core of everything we build. Over the years, we've continually introduced ways to help users stay safe and make informed app choices -- from parental controls to data safety transparency and app badges. We're constantly improving our policies and protections to encourage safe, high-quality apps on Google Play and stop bad actors before they cause harm. Apps on Google Play undergo rigorous reviews for safety and compliance with our policies. Last year, we shared that Google Play runs over 10,000 safety checks on every app we publish, and we continue to check and recheck apps after they'v ## Android Theft Protection Updates Add Authentication Controls and Recovery Safeguards DevFeed: [Android Theft Protection Updates Add Authentication Controls and Recovery Safeguards]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-01-27T16:59:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Android Security](), [LineageOS](), [Security](), [Authentication](), [passwords](), [Google]() Tags: [2025](), [android](), [android-security](), [authentication](), [banking](), [brazil](), [browser](), [feature](), [none](), [password](), [recovery](), [security](), [time](), [updates]() ### AI overview Google announces Android theft protection updates including more control over Failed Authentication Lock, expanded Identity Check coverage, longer lockout times after failed screen-lock attempts, and an optional security challenge for Remote Lock. ### Source excerpt Posted by Nataliya Stanetsky, Fabricio Ferracioli, Elliot Sisteron, Irene Ang of the Android Security Team Phone theft is more than just losing a device; it's a form of financial fraud that can leave you suddenly vulnerable to personal data and financial theft. That's why we're committed to providing multi-layered defenses that help protect you before, during, and after a theft attempt. Today, we're announcing a powerful set of theft protection feature updates that build on our existing protections, designed to give you greater peace of mind by making your device a much harder target for criminals. Stronger Authentication Safeguards We've expanded our security to protect you against an even wider range of threats. These updates are now available for Android devices running Android 16+. More User Control for Failed Authentications: In Android 15, we launched Failed Authentication Lock, a feature that automatically locks the device's screen after excessive failed authentication attempts. This feature is now getting a new dedicated enable/disable toggle in settings, giving you more granular control over your device's security. Expanding Identity Check to cover more: Early in 2025, we enabled Identity Check for Android 15+, which requires the user to utilize biometrics when performing certain actions outside of trusted places. Later in the year, we extended this safeguard to cover all features and apps that use the Android Biometric Prompt. This means that critical tools that utilize Biometric Prompt, like third-party banking apps and Google Password Manager, now automatically benefit from the additional security of Identity Check. Stronger Protection Against Screen Lock Guessing: We're making it much harder for a thief to guess your PIN, pattern, or password by increasing the lockout time after failed attempts. To ensure you aren't locked out by mistake (by a curious child, for instance), identical incorrect guesses no longer count toward your retry limit. Enhanced Rec ## Android Security: mobsfscan DevFeed: [Android Security: mobsfscan]() Original publisher: [Read original article]() Author: Matthew Dolan Published: 2026-01-16T17:51:35Z Content type: tutorial Language: en Sources: [Stories by Matthew Dolan on Medium]() Topics: [Android Security](), [Mobile Security](), [Security](), [GitHub Actions](), [CI/CD](), [GitHub](), [Docker Image]() Tags: [android-app-development](), [android-security](), [androiddev](), [build-secure-apps](), [ci-cd](), [docker-image](), [github](), [github-actions](), [mobile-security](), [security]() ### AI overview A tutorial on using the free, open-source mobsfscan tool to detect insecure code patterns in mobile applications. It focuses on running mobsfscan with GitHub Actions and uploading SARIF results to GitHub's Security tab. ### Source excerpt Not a medium member? "Read for free" Continue reading on Stackademic " ## Further Hardening Android GPUs DevFeed: [Further Hardening Android GPUs]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-12-09T17:00:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [GPU](), [Security](), [Android](), [Arm](), [SELinux](), [Kernel](), [Vulnerabilities]() Tags: [android](), [android-security](), [arm](), [gpu](), [kernel](), [none](), [security](), [selinux](), [vulnerabilities]() ### AI overview Google's Android Red Team and Arm analyzed the Mali GPU driver and firmware stack to reduce the driver's attack surface. The post describes using SELinux to restrict GPU IOCTLs that are intended for development, debugging, instrumentation, or deprecated use in production. ### Source excerpt Posted by Liz Prucka, Hamzeh Zawawy, Rishika Hooda, Android Security and Privacy Team Last year, Google's Android Red Team partnered with Arm to conduct an in-depth security analysis of the Mali GPU, a component used in billions of Android devices worldwide. This collaboration was a significant step in proactively identifying and fixing vulnerabilities in the GPU software and firmware stack. While finding and fixing individual bugs is crucial, and progress continues on eliminating them entirely, making them unreachable by restricting attack surface is another effective and often faster way to improve security. This post details our efforts in partnership with Arm to further harden the GPU by reducing the driver's attack surface. The Growing Threat: Why GPU Security Matters The Graphics Processing Unit (GPU) has become a critical and attractive target for attackers due to its complexity and privileged access to the system. The scale of this threat is significant: since 2021, the majority of Android kernel driver-based exploits have targeted the GPU. These exploits primarily target the interface between the User-Mode Driver (UMD) and the highly privileged Kernel-Mode Driver (KMD), where flaws can be exploited by malicious input to trigger memory corruption. Partnership with Arm Our goal is to raise the bar on GPU security, ensuring the Mali GPU driver and firmware remain highly resilient against potential threats. We partnered with Arm to conduct an analysis of the Mali driver, used on approximately 45% of Android devices. This collaboration was crucial for understanding the driver's attack surface and identifying areas that posed a security risk, but were not necessary for production use. The Right Tool for the Job: Hardening with SELinux One of the key findings of our investigation was the opportunity to restrict access to certain GPU IOCTLs. IOCTLs act as the GPU kernel driver's user input and output, as well as the attack surface. This approach builds on earlier k ## Android expands pilot for in-call scam protection for financial apps DevFeed: [Android expands pilot for in-call scam protection for financial apps]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-12-03T16:59:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Android](), [Security](), [Social engineering](), [Mobile](), [Google]() Tags: [android](), [android-security](), [google](), [mobile](), [none](), [safety](), [scams](), [screen-sharing](), [security](), [social-engineering]() ### AI overview Google is expanding Android's pilot for in-call scam protection to the United States with selected fintechs and banks, following pilots in the UK, Brazil, and India. The feature warns users when they open participating financial apps while screen sharing during a call from an unknown number, and provides a one-tap option to end the call and stop screen sharing. ### Source excerpt Posted by Aden Haussmann, Associate Product Manager and Sumeet Sharma, Play Partnerships Trust & Safety Lead Android uses the best of Google AI and our advanced security expertise to tackle mobile scams from every angle. Over the last few years, we've launched industry-leading features to detect scams and protect users across phone calls, text messages and messaging app chat notifications. These efforts are making a real difference in the lives of Android users. According to a recent YouGov survey1 commissioned by Google, Android users were 58% more likely than iOS users to report they had not received any scam texts in the prior week2. But our work doesn't stop there. Scammers are continuously evolving, using more sophisticated social engineering tactics to trick users into sharing their phone screen while on the phone to visit malicious websites, reveal sensitive information, send funds or download harmful apps. One popular scam involves criminals impersonating banks or other trusted institutions on the phone to try to manipulate victims into sharing their screen in order to reveal banking information or make a financial transfer. To help combat these types of financial scams, we launched a pilot earlier this year in the UK focused on in-call protections for financial apps. How the in-call scam protection works on Android When you launch a participating financial app while screen sharing and on a phone call with a number that is not saved in your contacts, your Android device3 will automatically warn you about the potential dangers and give you the option to end the call and to stop screen sharing with just one tap. The warning includes a 30-second pause period before you're able to continue, which helps break the 'spell' of the scammer's social engineering, disrupting the false sense of urgency and panic commonly used to manipulate you into a scam. Bringing in-call scam protections to more users on Android The UK pilot of Android's in-call scam protections has al ## Android Quick Share Support for AirDrop: A Secure Approach to Cross-Platform File Sharing DevFeed: [Android Quick Share Support for AirDrop: A Secure Approach to Cross-Platform File Sharing]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-11-20T17:00:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Android](), [cross-platform](), [Security & Privacy](), [interoperability](), [iOS](), [Google](), [Rust]() Tags: [android](), [android-security](), [cross-platform](), [google](), [interoperability](), [ios](), [none](), [rust](), [secure-by-design](), [security-privacy]() ### AI overview Google describes Quick Share interoperability with AirDrop, enabling two-way file sharing between Android and iOS devices starting with the Pixel 10 Family. The article explains the security measures used in the feature, including threat modeling, privacy reviews, penetration testing, and a Rust-based communication channel. ### Source excerpt Posted by Dave Kleidermacher, VP, Platforms Security & Privacy, Google Technology should bring people closer together, not create walls. Being able to communicate and connect with friends and family should be easy regardless of the phone they use. That's why Android has been building experiences that help you stay connected across platforms. As part of our efforts to continue to make cross-platform communication more seamless for users, we've made Quick Share interoperable with AirDrop, allowing for two-way file sharing between Android and iOS devices, starting with the Pixel 10 Family. This new feature makes it possible to quickly share your photos, videos, and files with people you choose to communicate with, without worrying about the kind of phone they use. Most importantly, when you share personal files and content, you need to trust that it stays secure. You can share across devices with confidence knowing we built this feature with security at its core, protecting your data with strong safeguards that have been tested by independent security experts. Secure by Design We built Quick Share's interoperability support for AirDrop with the same rigorous security standards that we apply to all Google products. Our approach to security is proactive and deeply integrated into every stage of the development process. This includes: Threat Modeling: We identify and address potential security risks before they can become a problem. Internal Security Design and Privacy Reviews: Our dedicated security and privacy teams thoroughly review the design to ensure it meets our high standards. Internal Penetration Testing: We conduct extensive in-house testing to identify and fix vulnerabilities. This Secure by Design philosophy ensures that all of our products are not just functional but also fundamentally secure. This feature is also protected by a multi-layered security approach to ensure a safe sharing experience from end-to-end, regardless of what platform you're on. Secure S ## Rust in Android: move fast and fix things DevFeed: [Rust in Android: move fast and fix things]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-11-13T16:59:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Android](), [Rust](), [Memory Safety](), [Vulnerabilities](), [C](), [C++](), [Linux]() Tags: [android](), [android-security](), [c](), [c-plus-plus](), [linux](), [memory-safety](), [none](), [programming](), [rust](), [security](), [software](), [vulnerabilities]() ### AI overview Google describes how Rust adoption in Android is associated with fewer memory safety vulnerabilities and faster software delivery. The article reports that memory safety vulnerabilities fell below 20% of total vulnerabilities in 2025, while Rust changes had lower rollback rates and spent less time in code review than comparable changes. ### Source excerpt Posted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in new code quickly yields durable and compounding gains. This year we look at how this approach isn't just fixing things, but helping us move faster. The 2025 data continues to validate the approach, with memory safety vulnerabilities falling below 20% of total vulnerabilities for the first time. Updated data for 2025. This data covers first-party and third-party (open source) code changes to the Android platform across C, C++, Java, Kotlin, and Rust. This post is published a couple of months before the end of 2025, but Android's industry-standard 90-day patch window means that these results are very likely close to final. We can and will accelerate patching when necessary. We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android's C and C++ code. But the biggest surprise was Rust's impact on software delivery. With Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one. In this post, we dig into the data behind this shift and also cover: How we're expanding our reach: We're pushing to make secure code the default across our entire software stack. We have updates on Rust adoption in first-party apps, the Linux kernel, and firmware. Our first rust memory safety vulnerability...almost: We'll analyze a near-miss memory safety bug in unsafe Rust: how it happened, how it was mitigated, and steps we're taking to prevent recurrence. It's also a good chance to answer the question "if Rust can have memory safety issues, why bother at all?" Building Better Software, Faster Developing an operating system requires the low-level control and predictability of systems programming languages like C, C++, and Rust. While Java and Kotlin are important for Android platform development, their role is complementary ## How Android and Google Messages protect users from mobile scams DevFeed: [How Android and Google Messages protect users from mobile scams]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-10-30T16:59:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Android](), [Cybersecurity](), [Security](), [Mobile](), [Google AI](), [iOS](), [Google](), [iphone](), [Messaging]() Tags: [ai](), [android](), [android-security](), [cybersecurity](), [google](), [google-ai](), [ios](), [iphone](), [messaging](), [mobile](), [none](), [pixel](), [protection](), [report](), [scams](), [security](), [smartphone](), [survey]() ### AI overview This article describes Android's layered protections against mobile scams, including defenses for malicious calls and messages and safety checks for RCS. It also presents a Google and YouGov survey comparing reported scam experiences and confidence among Android and iOS users in the U.S., India, and Brazil. ### Source excerpt Posted by Lyubov Farafonova, Product Manager, Phone by Google; Alberto Pastor Nieto, Sr. Product Manager Google Messages and RCS Spam and Abuse; Vijay Pareek, Manager, Android Messaging Trust and Safety As Cybersecurity Awareness Month wraps up, we're focusing on one of today's most pervasive digital threats: mobile scams. In the last 12 months, fraudsters have used advanced AI tools to create more convincing schemes, resulting in over $400 billion in stolen funds globally.ยน For years, Android has been on the frontlines in the battle against scammers, using the best of Google AI to build proactive, multi-layered protections that can anticipate and block scams before they reach you. Android's scam defenses protect users around the world from over 10 billion suspected malicious calls and messages every month2. In addition, Google continuously performs safety checks to maintain the integrity of the RCS service. In the past month alone, this ongoing process blocked over 100 million suspicious numbers from using RCS, stopping potential scams before they could even be sent. To show how our scam protections work in the real world, we asked users and independent security experts to compare how well Android and iOS protect you from these threats. We're also releasing a new report that explains how modern text scams are orchestrated, helping you understand the tactics fraudsters use and how to spot them. Survey shows Android users' confidence in scam protections Google and YouGov3 surveyed 5,000 smartphone users across the U.S., India, and Brazil about their scam experiences. The findings were clear: Android users reported receiving fewer scam texts and felt more confident that their device was keeping them safe. Android users were 58% more likely than iOS users to say they had not received any scam texts in the week prior to the survey. The advantage was even stronger on Pixel, where users were 96% more likely than iPhone owners to report zero scam texts4. At the other end o ## How Pixel and Android are bringing a new level of trust to your images with C2PA Content Credentials DevFeed: [How Pixel and Android are bringing a new level of trust to your images with C2PA Content Credentials]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-09-10T15:59:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Google](), [Android Security](), [Security](), [Mobile](), [Hardware](), [Generative AI]() Tags: [android](), [android-security](), [digital-signature](), [generative-ai](), [google](), [hardware](), [pixel](), [security]() ### AI overview Google describes how Pixel 10, Pixel Camera, and Google Photos will support C2PA Content Credentials to improve the provenance and verification of digital media. The article outlines Android-specific security capabilities, including Assurance Level 2, private certificate management, trusted timestamps, offline support, and hardware-backed protection, and says developers can apply the model to Android apps. ### Source excerpt Posted by Eric Lynch, Senior Product Manager, Android Security, and Sherif Hanna, Group Product Manager, Google C2PA Core At Made by Google 2025, we announced that the new Google Pixel 10 phones will support C2PA Content Credentials in Pixel Camera and Google Photos. This announcement represents a series of steps towards greater digital media transparency: The Pixel 10 lineup is the first to have Content Credentials built in across every photo created by Pixel Camera. The Pixel Camera app achieved Assurance Level 2, the highest security rating currently defined by the C2PA Conformance Program. Assurance Level 2 for a mobile app is currently only possible on the Android platform. A private-by-design approach to C2PA certificate management, where no image or group of images can be related to one another or the person who created them. Pixel 10 phones support on-device trusted time-stamps, which ensures images captured with your native camera app can be trusted after the certificate expires, even if they were captured when your device was offline. These capabilities are powered by Google Tensor G5, Titan M2 security chip, the advanced hardware-backed security features of the Android platform, and Pixel engineering expertise. In this post, we'll break down our architectural blueprint for bringing a new level of trust to digital media, and how developers can apply this model to their own apps on Android. A New Approach to Content Credentials Generative AI can help us all to be more creative, productive, and innovative. But it can be hard to tell the difference between content that's been AI-generated, and content created without AI. The ability to verify the source and history--or provenance--of digital content is more important than ever. Content Credentials convey a rich set of information about how media such as images, videos, or audio files were made, protected by the same digital signature technology that has secured online transactions and mobile apps for decades. I ## Android pKVM Achieves SESIP Level 5 Security Certification DevFeed: [Android pKVM Achieves SESIP Level 5 Security Certification]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-08-12T16:00:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Android](), [Android Security](), [Security](), [open-source-security](), [Google](), [virtualization](), [On-device AI]() Tags: [android](), [android-security](), [google](), [integrity](), [none](), [on-device-ai](), [open-source-security](), [security](), [standard](), [virtualization](), [vulnerability]() ### AI overview Google announces that protected KVM (pKVM), the hypervisor powering the Android Virtualization Framework, achieved SESIP Level 5 certification after evaluation by Dekra against the TrustCB SESIP scheme. The article says this certification is intended to support highly critical isolated workloads, including on-device AI handling personalized data, and provide a common open-source security foundation for Android device manufacturers. ### Source excerpt Posted by Dave Kleidermacher, VP Engineering, Android Security & Privacy Today marks a watershed moment and new benchmark for open-source security and the future of consumer electronics. Google is proud to announce that protected KVM (pKVM), the hypervisor that powers the Android Virtualization Framework, has officially achieved SESIP Level 5 certification. This makes pKVM the first software security system designed for large-scale deployment in consumer electronics to meet this assurance bar. Supporting Next-Gen Android Features The implications for the future of secure mobile technology are profound. With this level of security assurance, Android is now positioned to securely support the next generation of high-criticality isolated workloads. This includes vital features, such as on-device AI workloads that can operate on ultra-personalized data, with the highest assurances of privacy and integrity. This certification required a hands-on evaluation by Dekra, a globally recognized cybersecurity certification lab, which conducted an evaluation against the TrustCB SESIP scheme, compliant to EN-17927. Achieving Security Evaluation Standard for IoT Platforms (SESIP) Level 5 is a landmark because it incorporates AVA_VAN.5, the highest level of vulnerability analysis and penetration testing under the ISO 15408 (Common Criteria) standard. A system certified to this level has been evaluated to be resistant to highly skilled, knowledgeable, well-motivated, and well-funded attackers who may have insider knowledge and access. This certification is the cornerstone of the next-generation of Android's multi-layered security strategy. Many of the TEEs (Trusted Execution Environments) used in the industry have not been formally certified or have only achieved lower levels of security assurance. This inconsistency creates a challenge for developers looking to build highly critical applications that require a robust and verifiable level of security. The certified pKVM changes this p [Next page]()