Loading story…
Google has released Android 17, publishing the source code to AOSP under the tag android-17.0.0_r1 and beginning rollout to supported Pixel devices, with broader availability planned across OEMs including HONOR, Lenovo, OnePlus, OPPO, vivo, Xiaomi, and others. Google also made Generic System Images available for ARM64 and x86_64, while the platform adds major usability and device features such as foldable enhancements, App Bubbles, Handoff support, VVC/H.266 video, RAW14, HE-AAC, BLE hearing-aid improvements, and OpenJDK 25 integration.
The release introduces a broad set of security and privacy changes, including tighter controls for contacts, location, and local network access, expanded one-time-password handling beyond SMS, stricter restrictions on dynamic code loading, stronger lost-device protections, improved threat detection, enhanced Advanced Protection, and stricter PIN retry limits. Google also added Certificate Transparency-related enhancements, support for HPKE cryptography and ML-DSA APK signatures, and continued restrictions on cleartext traffic, alongside Pixel-specific updates delivered through the June Pixel Drop.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
Google announced Android 17 alongside the June 2026 Pixel Drop, with rollout starting on Pixel devices first and broader Android device availability planned throughout 2026. The update introduced new usability features and security changes including tighter permissions, stronger lost-device protections, improved threat detection, enhanced Advanced Protection, and stricter PIN retry limits.
Google announced Android 17 and published its source code in the Android Open Source Project repository under the tag android-17.0.0_r1. The release was made available for supported Pixel devices, with factory images and GSI images for ARM64 and x86_64 also published.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
33 references tracked. Mallory keeps watching after this page renders.
zdnet.fr
Open sourcesecurityonline.info
Open sourcehelpnetsecurity.com
Open sourceghacks.net
Open sourcedeveloper.android.com
Open sourcedeveloper.android.com
Open sourcedeveloper.android.com
Open sourcedeveloper.android.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Apple released an *iOS/iPadOS 26.4 developer beta* that adds **end-to-end encryption (E2EE) for RCS messaging** in limited testing, with availability constrained by device/carrier support and currently limited to **Apple-to-Apple** RCS conversations. The implementation is tied to upgrading to **RCS Universal Profile 3.0** built on the **Messaging Layer Security (MLS)** protocol, aligning with the GSMA’s prior move to standardize E2EE for RCS. The beta also expands platform hardening by allowing apps to opt into the full protections of **Memory Integrity Enforcement (MIE)** (beyond the previously available “Soft Mode”), and reporting indicates Apple may enable **Stolen Device Protection** by default in this release line. Google released the first *Android 17 beta* with multiple privacy/security changes aimed at tightening network and cryptographic defaults and improving user control. Android 17 **deprecates** the `android:usesCleartextTraffic` manifest attribute; apps targeting Android 17+ that set `usesCleartextTraffic="true"` without a **Network Security Configuration** will have cleartext traffic blocked by default, pushing developers toward more granular policy via configuration files. The beta also introduces a public **HPKE (Hybrid Public Key Encryption)** Service Provider Interface, adds user preference controls for **VoIP call history integration**, and expands **Wi‑Fi ranging** for proximity detection and secure peer-to-peer discovery.
Jun 29, 2026
Google's upcoming **Android 17** release is being discussed through early beta builds, leaks, and hands-on coverage of new AI-assisted features. Reported changes include a broader visual redesign tied to *Material 3 Expressive*, possible blur-heavy interface elements, and additional privacy-focused updates expected to be highlighted during the platform's public rollout. Early testing by Google and device makers indicates the next Android version is already in active development ahead of a likely mid-year stable release. One reported capability is **AI-powered notification summaries** on supported Pixel devices, which condense long messages and display them on the lock screen using on-device processing. That feature appears consistent with the broader push toward AI enhancements in Android, but the hands-on report focuses on current Pixel functionality rather than the broader Android 17 leak cycle. The material is **not fluff** because it contains substantive product and platform details with security and privacy implications, even though it is not about a breach, exploit, or vulnerability disclosure.
Jun 29, 2026
Google released the second beta of **Android 17** with new privacy-focused platform behaviors and APIs aimed at reducing unnecessary access to sensitive data. Changes include a system-level **Contacts Picker** that grants apps only temporary access to user-selected contacts (including across personal/work profiles), a new `ACCESS_LOCAL_NETWORK` runtime permission to control discovery/connection to LAN devices (with an alternative path via system-mediated device pickers), and expanded safeguards for SMS one-time passwords by delaying most apps’ programmatic access to OTP messages for three hours (with exemptions for default SMS and approved companion apps, and guidance to use SMS Retriever/SMS User Consent APIs). Microsoft is testing **Windows 11** security and performance improvements for batch/CMD script execution in Insider Preview builds by adding an optional “secure processing mode” that prevents batch files from being modified while running. Administrators can enable it via the `LockBatchFilesInUse` registry value under `HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor` or via the `LockBatchFilesWhenInUse` application manifest control, reducing repeated signature validation when code integrity is enabled. Separately, commentary on **Windows telemetry** reiterates that Microsoft collects diagnostic data and suggests users can inspect telemetry themselves, but it does not describe a specific new security incident or vulnerability disclosure.
Jun 29, 2026