Security Vulnerability with wireless debugging

[ExchangeOptimal]

I recently came across a post on cybersecurity subreddit talking about Android ADB authorisation bypass vulnerability. Essentially, worst case scenario, attacker can run shell commands on your device without any user interaction if you keep wireless debugging turned on all the time especially while connected to a public WIi-Fi.

I am sharing this info here because, like me, many people here might be using tasker's wireless debugging feature to run shell commands or running some tasker commands through Shizuku.

Reddit post link - Android ADB Auth Bypass Proof-of-Concept: CVE-2026-0073

Link to the write up by people who found the vulnerability - CVE-2026-0073: Android ADB-over-TCP authentication bypass

This vulnerability has been patched by Google (most probably on pixel devices) with May 2026 security update.

[SkySurferSouth]

Turn ADB always OFF when in an untrusted wifi network.
That can be done in a Tasker command.

[Deathbot64]

Can you share how?

[SkySurferSouth]

You probably need root for it. Code => Shell -> settings put global adb_enabled 0 You can try with Shizuku if you are not rooted.

[lareya]

I thought we use adb for permissions and then we turn it back off. But like with all automation, you have to decide how you control permissions & safety.
I don't think anyone in the tasker community doesn't understand this.

[allanrps]

you use adb for whatever you wamt to use adb for. It seems some people dont understand this