CVE-2026-0073Disclosure(google / android)

CRITICALCVSS 8.8 · HIGH

Exploitation observed; activity peaked at 33 mentions and remains active

Immediate actions

  • Patch google android systems immediately
  • Assume compromise if assets are exposed
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: Immediate (within 24h)

NVD description

In adbd_tls_verify_cert of auth.cpp, there is a possible bypass of wireless ADB mutual authentication due to a logic error in the code. This could lead to remote (proximal/adjacent) code execution as the shell user with no additional execution privileges needed. User interaction is not needed for exploitation.

8.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-303

Priority

CRITICAL

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

DECLINING

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • android

Threat summary

  • Active exploitation appears in 6 classified signals
  • Public PoC and exploit tooling are both present
  • Patch or workaround signal is available
  • 187 mentions across 38 observed days

What's happening

  • Active exploitation reported across 6 signals
  • Exploit tool or code specified in 16 signals
  • PoC mentioned or linked in 46 signals
  • Patch or workaround mentioned in 71 signals
  • Technical details provided in 136 signals
  • Disclosure: 61 classified signals
  • Peaked 36d ago at 33 mentions (2026-05-05); latest day: 1
  • 187 total mentions across 38 days

Affected systems

Vendors
Products
android

3 versions affected across 1 product

Deep dive

Activity timeline187 mentions / 38d
08172533Mentions · 2026-05-04: 6Mentions · 2026-05-05: 33Mentions · 2026-05-06: 21Mentions · 2026-05-07: 16Mentions · 2026-05-08: 5Mentions · 2026-05-09: 7Mentions · 2026-05-10: 7Mentions · 2026-05-11: 7Mentions · 2026-05-12: 10Mentions · 2026-05-13: 4Mentions · 2026-05-14: 7Mentions · 2026-05-15: 1Mentions · 2026-05-16: 1Mentions · 2026-05-17: 10Mentions · 2026-05-20: 3Mentions · 2026-05-23: 1Mentions · 2026-05-26: 1Mentions · 2026-06-03: 9Mentions · 2026-06-04: 1Mentions · 2026-06-08: 2Mentions · 2026-06-09: 1Mentions · 2026-06-14: 1Mentions · 2026-06-19: 1Mentions · 2026-06-21: 7Mentions · 2026-06-25: 4Mentions · 2026-07-03: 1Mentions · 2026-07-12: 1Mentions · 2026-07-15: 1Mentions · 2026-07-16: 1Mentions · 2026-07-23: 1Mentions · 2026-07-25: 1Mentions · 2026-07-26: 2Mentions · 2026-07-28: 7Mentions · 2026-07-29: 1Mentions · 2026-08-11: 2Mentions · 2026-08-20: 1Mentions · 2026-08-29: 1Mentions · 2026-09-01: 1PoC Mentioned / Linked · 2026-05-05: 6PoC Mentioned / Linked · 2026-05-06: 2PoC Mentioned / Linked · 2026-05-07: 6PoC Mentioned / Linked · 2026-05-08: 3PoC Mentioned / Linked · 2026-05-09: 1PoC Mentioned / Linked · 2026-05-11: 5PoC Mentioned / Linked · 2026-05-12: 3PoC Mentioned / Linked · 2026-05-13: 3PoC Mentioned / Linked · 2026-05-20: 1PoC Mentioned / Linked · 2026-06-03: 1PoC Mentioned / Linked · 2026-06-21: 2PoC Mentioned / Linked · 2026-06-25: 3PoC Mentioned / Linked · 2026-07-03: 1PoC Mentioned / Linked · 2026-07-16: 1PoC Mentioned / Linked · 2026-07-26: 2PoC Mentioned / Linked · 2026-07-28: 5PoC Mentioned / Linked · 2026-08-11: 1Exploit Tool / Code · 2026-05-05: 1Exploit Tool / Code · 2026-05-07: 2Exploit Tool / Code · 2026-05-08: 2Exploit Tool / Code · 2026-05-11: 3Exploit Tool / Code · 2026-05-12: 2Exploit Tool / Code · 2026-05-20: 1Exploit Tool / Code · 2026-06-03: 1Exploit Tool / Code · 2026-06-09: 1Exploit Tool / Code · 2026-06-25: 2Exploit Tool / Code · 2026-07-03: 1Active Exploitation · 2026-05-11: 1Active Exploitation · 2026-05-17: 1Active Exploitation · 2026-06-03: 1Active Exploitation · 2026-06-09: 1Active Exploitation · 2026-07-12: 1Active Exploitation · 2026-07-28: 1Patch / Workaround · 2026-05-04: 2Patch / Workaround · 2026-05-05: 20Patch / Workaround · 2026-05-06: 13Patch / Workaround · 2026-05-07: 4Patch / Workaround · 2026-05-08: 2Patch / Workaround · 2026-05-09: 6Patch / Workaround · 2026-05-10: 2Patch / Workaround · 2026-05-11: 1Patch / Workaround · 2026-05-12: 3Patch / Workaround · 2026-05-13: 1Patch / Workaround · 2026-05-14: 5Patch / Workaround · 2026-05-16: 1Patch / Workaround · 2026-05-17: 5Patch / Workaround · 2026-05-23: 1Patch / Workaround · 2026-05-26: 1Patch / Workaround · 2026-06-21: 1Patch / Workaround · 2026-07-25: 1Patch / Workaround · 2026-07-28: 1Patch / Workaround · 2026-09-01: 1Technical Details · 2026-05-04: 5Technical Details · 2026-05-05: 21Technical Details · 2026-05-06: 18Technical Details · 2026-05-07: 13Technical Details · 2026-05-08: 4Technical Details · 2026-05-09: 4Technical Details · 2026-05-10: 5Technical Details · 2026-05-11: 4Technical Details · 2026-05-12: 8Technical Details · 2026-05-13: 3Technical Details · 2026-05-14: 5Technical Details · 2026-05-16: 1Technical Details · 2026-05-17: 6Technical Details · 2026-05-20: 2Technical Details · 2026-05-23: 1Technical Details · 2026-05-26: 1Technical Details · 2026-06-03: 8Technical Details · 2026-06-04: 1Technical Details · 2026-06-08: 1Technical Details · 2026-06-09: 1Technical Details · 2026-06-14: 1Technical Details · 2026-06-21: 5Technical Details · 2026-06-25: 4Technical Details · 2026-07-03: 1Technical Details · 2026-07-12: 1Technical Details · 2026-07-15: 1Technical Details · 2026-07-16: 1Technical Details · 2026-07-25: 1Technical Details · 2026-07-26: 1Technical Details · 2026-07-28: 6Technical Details · 2026-07-29: 1Technical Details · 2026-09-01: 105-0405-0705-1005-1305-1605-2306-0406-1406-2507-1507-2507-2908-2909-01
Signal classification6 categories
Disclosure
6132.6%
Patch
5831.0%
PoC
3619.3%
General
2513.4%
Active Exploitation
52.7%
Exploit
21.1%
Referenced assets83 URLs
By indicator
Classification over time
DateTotalLabels
2026-05-046
Disclosure4General2
2026-05-0533
Disclosure10General4Patch18PoC1
2026-05-0621
Disclosure6General1Patch13PoC1
2026-05-0716
Disclosure7General1Patch3PoC5
2026-05-085
General1Patch1PoC3
2026-05-097
Disclosure2Patch5
2026-05-107
Disclosure4General1Patch2
2026-05-117
Active Exploitation1Exploit1General1PoC4
2026-05-1210
Disclosure4General1Patch2PoC3
2026-05-134
Disclosure2PoC2
2026-05-147
Disclosure3Patch4
2026-05-151
General1
2026-05-161
Patch1
2026-05-1710
Active Exploitation1Disclosure2General2Patch5
2026-05-203
Disclosure1General1PoC1
2026-05-231
Patch1
2026-05-261
Patch1
2026-06-039
Disclosure6Exploit1General2
2026-06-041
Disclosure1
2026-06-082
Disclosure1General1
2026-06-091
Active Exploitation1
2026-06-141
Disclosure1
2026-06-191
General1
2026-06-217
Disclosure4Patch1PoC2
2026-06-254
General1PoC3
2026-07-031
PoC1
2026-07-121
Active Exploitation1
2026-07-151
PoC1
2026-07-161
PoC1
2026-07-231
General1
2026-07-251
Patch1
2026-07-262
PoC2
2026-07-287
Active Exploitation1PoC6
2026-07-291
Disclosure1
2026-08-112
Disclosure1General1
2026-08-201
General1
2026-08-291
General1
2026-09-011
Disclosure1
Full discourse20 posts
  • Cyber Security News@The_Cyber_News
    Disclosure

    🛡️ Critical Android Zero-Click Vulnerability Grants Remote Shell Access Source: https://cybersecuritynews.com/android-zero-click-vulnerability/ Google has published the May 2026 Android Security Bulletin, alerting the ecosystem to a highly severe remote code execution (RCE) flaw. Tracked as CVE-2026-0073, this critical vulnerability resides deep within the core Android System component. It allows an attacker to gain remote shell access without requiring a single tap, download, or click from the device owner. Threat actors can launch this zero-click attack proximally, meaning they only need to be on the same local network or in physical proximity to exploit a vulnerable mobile device. #cybersecuritynews #Android

    Post summary

    Google announced CVE-2026-0073, a critical zero‑click RCE vulnerability in Android’s core system that allows attackers to gain remote shell access without any user interaction.

    23309411.2K618109.8K
    67.1K followersView on X
  • Mololuwa | Cybersecurity - (The God Complex)@cyber_rekk
    PoC

    Demo of recently published android zero click RCE via wireless debugging, (CVE-2026-0073) Educational purposes only Check Mobile hacker for more https://t.co/cteIqJ7aBE

    Post summary

    The post announces a demo of a recently published Android zero‑click RCE (CVE‑2026‑0073) via wireless debugging, flagged for educational use, and directs readers to a mobile hacker link for more information.

    11106268749240.1K
    23.1K followersView on X
  • Cyber Security News@The_Cyber_News
    PoC

    ⚠️ PoC Exploit Released for Android 0-Click Flaw that Enables Remote Shell Access Source: https://cybersecuritynews.com/poc-exploit-android-zero-click-vulnerability/ Google's May 2026 Android Security Bulletin has revealed a critical zero-click vulnerability in the core Android System. The CVE-2026-0073 flaw in Android’s adbd daemon lets nearby threat actors remotely gain full shell access without victim interaction. An attacker must first establish a TCP connection, successfully negotiate the STLS upgrade sequence, and then supply the malicious cross-algorithm certificate. To proactively reduce attack surfaces, users should turn off wireless debugging on untrusted networks and revoke authorizations for unknown debugging hosts. #cybersecuritynews #Android

    Post summary

    A PoC exploit for CVE‑2026‑0073 has been released, detailing a zero‑click remote shell vulnerability in Android’s adbd daemon, and the post offers mitigation steps without evidence of active exploitation.

    10112145717129.2K
    68.9K followersView on X
  • Ashok Mor@_techibee
    Patch

    🚨 Android users, update your phone ASAP! Google’s May 2026 Android Security Bulletin patches a critical zero-click vulnerability (CVE-2026-0073) that could let attackers gain remote shell access with NO user interaction required. Affected versions: 📱 Android 14 📱 Android 15 📱 Android 16 The flaw impacts the System component / adbd and is serious enough that Samsung, Pixel & other OEMs are already pushing emergency patches. Check your security patch level: Settings > Security & Privacy > Android Security Update If your device shows 2026-05-01 or later, you’re protected. This is exactly why monthly Android security updates matter. Don’t ignore them. #Android #CyberSecurity #Android16 #Google #Samsung

    Post summary

    Google has fixed CVE‑2026‑0073, a zero‑click remote shell vulnerability, and urges Android users to apply the May 2026 security patch to remain protected.

    2521329713559.1K
    11.4K followersView on X
  • GrapheneOS@GrapheneOS
    Patch

    CVE-2026-0073 is a Critical severity Remote Code Execution (RCE) vulnerability included as the only vulnerability fixed in the May 2026 Android Security Bulletin. GrapheneOS first shipped the patch in our 2026030501 security preview release on March 5th. It also isn't nearly as severe as it sounds. This was a bypass for TLS client certificate authentication in the Android Debug Bridge (ADB) for the Wireless debugging feature. It's only relevant to users enabling developer options, enabling Android Debug Bridge and then enabling Wireless debugging. Wireless debugging is disabled on reboot. Our security preview releases are recommended in the initial setup wizard via a dedicated page with toggle that's enabled by default. Existing users who weren't shown the page received a notification at boot opening a similar page with a save button. It reappears until a choice is made either way.

    Post summary

    The post announces that CVE‑2026‑0073, a critical RCE affecting ADB Wireless debugging, has been patched by GrapheneOS and notes the patch was available in a preview release, while indicating the real‑world severity is less than initially feared.

    32013452020.5K
    127.0K followersView on X
  • m4rio@m4rio_eth
    Patch

    Android just patched a critical zero-click RCE. CVE-2026-0073 affects the Android System component, specifically `adbd`, and can reportedly lead to remote code execution with no user interaction required. No tap. No download. No “open this file.” The attacker only needs to be nearby or on the same local network, which makes this especially relevant for places like airports, conferences, hotels, offices, and shared Wi-Fi environments. The `adbd` part is what makes this interesting. This is the Android Debug Bridge daemon used for device communication and debugging workflows, not some random app-level component. Reports say Android 14, 15, 16, and 16-QPR2 are affected. https://source.android.com/docs/security/bulletin/2026/2026-05-01

    Post summary

    Android has released a patch for CVE‑2026‑0073, a zero‑click remote code execution vulnerability in the adbd daemon that requires local network proximity. Affected Android versions 14‑16 are addressed in the latest security bulletin.

    834417011518.3K
    4.1K followersView on X
  • Ovi@0x0v1
    Disclosure

    Today we are disclosing CVE-2026-0073: A critical no-interaction proximal/adjacent remote code execution vulnerability in adbd's ADB-over-TCP authentication path. Full technical write-up + exploit flow: https://barghest.asia/blog/cve-2026-0073-adb-tls-auth-bypass/

    Post summary

    The text discloses CVE‑2026‑0073, a remote code execution flaw in Android’s ADB-over-TCP, and supplies a link to a full technical write‑up and exploit flow.

    32941068313.7K
    830 followersView on X
  • GrapheneOS@GrapheneOS
    Patch

    @JeffSte17327059 @gravax @alexis_roussel CVE-2026-0073 was included in the May 2026 ASB as a critical severity RCE vulnerability. GrapheneOS shipped the patch in March 2026. GrapheneOS is the only AOSP-based OS shipped all the patches quickly. It also has literally hundreds of upstream security patches shipped earlier.

    Post summary

    The post announces that CVE‑2026‑0073, a critical RCE in the May 2026 ASB, was patched by GrapheneOS as of March 2026, underscoring timely mitigation.

    2110168911.3K
    129.9K followersView on X
  • أوس بن فواز الفوزان@Awsffcs
    Patch

    🚨 ثغرة خطيرة في #أندرويد تستدعي الانتباه جوجل نشرت نشرة أمان مايو 2026 وحذرت من ثغرة حرجة باسم CVE-2026-0073 من نوع تنفيذ كود عن بعد #RCE داخل مكون أساسي في نظام أندرويد. الخطير في الموضوع أنها من نوع {النقرة الصفرية}، يعني المهاجم ما يحتاج منك تضغط رابط، ولا تحمل ملف، ولا حتى تتفاعل معه. يكفي يكون قريب منك أو على نفس الشبكة المحلية حتى يحاول استغلال الجهاز المصاب والوصول إلى قشرة النظام عن بعد. 💡نصيحتي: حدث جهازك فور وصول التحديث، وتجنب الشبكات العامة قدر الإمكان، ولا تستهين بتحديثات الأمان لأنها أحيانًا تكون خط الدفاع الأول👍👍👍👍 #السعوديه #عاجل_الآن #الأمن_السيبراني #ثغرات #CyberSecurity #Android #تقنية #الوعي_الرقمي

    Post summary

    The post alerts about the zero‑click RCE vulnerability CVE-2026-0073 affecting Android, warns of potential exploitation on local networks, and stresses the importance of applying updates.

    1170704717.7K
    4.7K followersView on X
  • Keystone Hardware Wallet@KeystoneWallet
    Patch

    🚨 Your Android phone can be hacked without you clicking anything. Google just disclosed CVE-2026-0073 - a critical vulnerability affecting millions of devices. No app install. No phishing link. No interaction. Just proximity to a compromised device or shared network. Once in, attackers may potentially: → read clipboard → capture screenshots → inject fake overlays → monitor sessions Your legitimate wallet app becomes a surveillance device. → Seed phrases are captured when viewed. → Clipboard hijacked mid-transaction. → Fake prompts that look identical to real ones. The wallet app is fine, but the OS beneath it is not. If the OS is compromised, the wallet inherits the compromise. Immediate actions: → Update Android now (patch: May 1, 2026+) → Install Google Play system updates → Avoid public networks until patched → Move significant holdings off mobile Mobile phones are not vaults. They're internet-connected attack surfaces with access to everything you type, see, and sign. Hardware wallets isolate keys from the OS - air-gapped, offline, unreachable even if your phone is hacked. With Keystone, signing happens offline. Details are displayed on-device. QR-only keeps the hackers at bay. Your phone can be hacked. Your keys cannot.

    Post summary

    Google has announced a critical Android vulnerability (CVE-2026-0073) that allows attackers to compromise the OS without user interaction, leading to clipboard theft and fake overlays, and it provides a patch date and remediation steps.

    3274772316.0K
    63.3K followersView on X
  • Nicolas Krassas@Dinosn
    PoC

    Android ADB Auth Bypass Proof-of-Concept: CVE-2026-0073 https://barghest.asia/blog/cve-2026-0073-adb-tls-auth-bypass/

    Post summary

    The blog post announces a Proof‑of‑Concept for CVE‑2026‑0073, showcasing an Android ADB authentication bypass, but provides no evidence of active exploitation, patches, or false positives.

    013061344.4K
    158.1K followersView on X
  • xvonfers@xvonfers
    Disclosure

    (CVE-2026-0073)[469080888][adb][auth]bypass of wireless ADB mutual authentication -> 0-click RCE(proximal/adjacent) as the shell user with no additional execution privileges needed https://android.googlesource.com/platform/packages/modules/adb/+/refs/heads/main/daemon/auth.cpp https://t.co/jDBImYbNP3

    Post summary

    The post announces CVE-2026-0073, a wireless ADB authentication bypass that allows 0‑click remote code execution, linking to source code but without evidence of active exploitation or mitigation.

    27350328.8K
    5.0K followersView on X
  • blackorbird@blackorbird
    PoC

    A critical no-interaction proximal/adjacent remote code execution vulnerability in adbd's ADB-over-TCP authentication path. CVE-2026-0073 https://barghest.asia/blog/cve-2026-0073-adb-tls-auth-bypass/ POC https://github.com/MartinPSDev/CVE-2026-0073-Android-ADBD-bypass-POC/blob/main/adb_tls_auth_bypass.py Developer options are enabled. ADB-over-TCP is enabled through Wireless debugging or another exposure of the platform TCP service.adbd /data/misc/adb/adb_keys contains at least one previously paired RSA ADB host key.

    Post summary

    The post announces CVE‑2026‑0073, describes a critical remote code execution flaw in adbd’s ADB‑over‑TCP authentication path, and shares a proof‑of‑concept script, but does not mention active exploitation, patches, or false‑positive claims.

    06032183.6K
    42.7K followersView on X
  • Welsh ICP Conviction 🏴󠁧󠁢󠁷󠁬󠁳󠁿🏉@ICPLEGEND1966
    Disclosure

    🚨 $ICP BY @dfinity FIXES THE REAL PROBLEM: CENTRALIZED TRUST BREAKS Google just confirmed a Critical Android zero-click vulnerability. CVE-2026-0073 can allow remote adjacent-network code execution as the Android shell user with no user interaction required. No click. No app install. No phishing link. No warning screen. The flaw sits in Android’s wireless ADB authentication logic, where a trusted debugging channel can be bypassed if the attacker is on the same local network. That is the real lesson. Modern infrastructure is full of hidden trust assumptions: centralized devices, centralized update chains, developer backdoors, cloud dependency, privileged admin channels, local network exposure, human patch delays. This is why $ICP matters. ICP is not just another blockchain moving tokens around. ICP is sovereign compute. ICP is full-stack onchain infrastructure. ICP runs frontend, backend, data and logic inside tamper-resistant canister smart contracts. ICP removes the need for traditional centralized servers. ICP reduces dependency on exposed admin panels, cloud dashboards, passwords, APIs and weak Web2 trust layers. When apps run fully onchain, the attack surface changes. No centralized server to seize. No cloud database to leak. No hidden backend to compromise. No AWS-style admin stack sitting behind the app. No bridge dependency for native multi-chain logic through Chain Fusion. No user gas friction due to reverse gas. Countries need this. Enterprises need this. AI agents need this. Critical infrastructure needs this. The world keeps patching symptoms. $ICP by @dfinity is building the architecture that removes entire classes of failure. Android needs an update. The internet needs an upgrade. That upgrade is ICP. If you value my work and want to support more $ICP research and content, contributions are appreciated: ICP address: 1e672d038cebc619d93186418fa98f6499dbdb9cfdfac54f366c61a4a4ee4362 #ICP #DFINITY #InternetComputer #CyberSecurity #ZeroClick #Web3 #AI #Cloud #SovereignCloud https://www.forbes.com/sites/daveywinder/2026/05/05/google-confirms-critical-android-0-click-vulnerability-update-now/

    Post summary

    Google has confirmed the existence of CVE‑2026‑0073, a critical Android zero‑click vulnerability enabling code execution over a local network. No PoC, exploit code, patch, or evidence of active exploitation is provided.

    0120420632
    1.5K followersView on X
  • XiaomiTime@timexiaomi
    Patch

    Xiaomi rolls out May 2026 security patch across Xiaomi/Redmi/POCO. - Fixes critical RCE CVE-2026-0073 in May patch - Regions: Global, EEA, India, Russia, Taiwan; HyperOS rollout staged - Affects Xiaomi 15 Ultra, 15T, REDMI 15A/17/ A7 Pro/ Pad 2 Pro, … https://ift.tt/8hf5sR1

    Post summary

    Xiaomi announces a May 2026 security patch that fixes the critical RCE vulnerability CVE-2026-0073 for multiple devices, with no indications of exploits or active attacks.

    0403512.3K
    12.3K followersView on X
  • MehrdadLinux@Mehrdadlinux
    Patch

    ⚠️ گوگل داره به بهانه یک بی‌ نماز در مسجد را میبنده🥴 میگه سر جریان CVE-2026-0073 سرویس ADB باید فقط به اینترفیس wlan0 محدود کنیم و اتصال به localhost نداشته باشیم😡 نتیجه جلوی ضبط تماس ها با Shizuku گرفته میشه 😤 کانال تلگرام توضیح کامل دادم https://t.me/MehrdadLinuxchannel/1140 https://t.co/WspUxR06xB

    Post summary

    The post advises limiting the ADB service to wlan0 as a workaround for CVE-2026-0073 to prevent call recording via Shizuku, with details shared in a Telegram channel.

    2102961.4K
    4.2K followersView on X
  • Dark Web Informer@DarkWebInformer
    Disclosure

    CVE-2026-0073: Zero-Click RCE Flaw in Android's Wireless ADB Bypasses Authentication https://darkwebinformer.com/cve-2026-0073-zero-click-rce-flaw-in-androids-wireless-adb-bypasses-authentication/

    Post summary

    The entry announces CVE‑2026‑0073, a zero‑click remote code execution flaw in Android’s Wireless ADB that bypasses authentication. No proof of concept, exploit tool, active exploitation, patch, or debunking is discussed.

    1602293.7K
    222.6K followersView on X
  • Gray Hats@the_yellow_fall
    PoC

    BARGHEST reveals CVE-2026-0073: a zero-click Android ADB bypass over Wi-Fi. Public PoC and exploit details are now live. Secure your mobile device today! #AndroidSecurity #ADB #CVE #InfoSec #CyberSecurity #ZeroClick #MobileHacking #PoC #ExploitAlert https://securityonline.info/android-adb-auth-bypass-cve-2026-0073-public-poc/ https://t.co/rVK9g0QUGq

    Post summary

    The tweet announces that a public proof‑of‑concept and exploit details for CVE‑2026‑0073, a zero‑click Android ADB bypass over Wi‑Fi, are available online.

    1501352.0K
    12.5K followersView on X
  • ngCERT@ngCERTofficial
    General

    ngCERT has issued an advisory on a Critical Zero-Click Vulnerability, tracked as CVE-2026-0073 on its website. Organisations are strongly advised to take necessary steps to safeguard their systems. For further technical details, visit https://cert.gov.ng/advisories/critical-android-zero-click-vulnerability https://t.co/MrfDTMWJsZ

    Post summary

    The advisory alerts about a critical zero‑click CVE‑2026‑0073 and urges precautions, but it provides no PoC, exploit details, patch information, or technical specifics.

    0110121493
    1.3K followersView on X
  • XiaomiTime@timexiaomi
    Patch

    Xiaomi HyperOS May 2026 Security Update ahead of OTA. - Fixes CVE-2026-0073, critical RCE - High risk: no user interaction, proximity attack - Adbd may get partial protection via Google Play System Updates - Rollout across HyperOS 2/3 on Android 14–… https://ift.tt/jHzvBnG

    Post summary

    Xiaomi HyperOS is rolling out an OTA update that patches CVE-2026-0073, a critical remote code execution vulnerability, and offers partial protection via Google Play System Updates. The announcement focuses on the availability of the patch and the vulnerability details rather than exploitation evidence.

    0101311.0K
    12.3K followersView on X
CPE platform detail6 entries

6 of 6 entries

PartVendorProductVersionTarget SWTarget HW
OSgoogleandroid14.0--
OSgoogleandroid15.0--
OSgoogleandroid16.0--
OSgoogleandroid16.0--
OSgoogleandroid16.0--
OSgoogleandroid16.0--

Explore more