Skip to main content
← Vulnerabilities

About Time Technologies|Herowatch Mini - Missing Authentication

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts give no workaround. The only condition stated is that the ADB service must be reachable, so limiting network access to that service is the step the facts point to, but they do not confirm it as an official fix.

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Exposure: unknown (data gap). Advisories don't say whether default setups are affected
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

CVE-2026-121816 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Herowatch Mini; no fixed version is listed yet.

Published
Last modified
Published
Not listed in CISA KEV
0.35% · 29th percentile
15/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Herowatch Mini from About Time Technologies contains a missing-authentication flaw in its ADB service. An attacker on the same local network segment can connect without logging in and get an ADB shell, which gives them access to device resources and related operations.

Read the original description

Herowatch Mini developed by About Time Technologies has a Missing Authentication vulnerability. Unauthenticated remote attackers can connect to the affected device's ADB service and obtain an ADB shell, thereby accessing device resources or performing related operations.

What to do

  • Workaround: The checked facts give no workaround. The only condition stated is that the ADB service must be reachable, so limiting network access to that service is the step the facts point to, but they do not confirm it as an official fix.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • About Time Technologies Herowatch Mini

    All versions

Evidence 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121816

Is CVE-2026-121816 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The device does not require authentication before its ADB service is reached, so a network attacker who can connect to that service can obtain an ADB shell. From there, the attacker can access device resources or perform related operations.Source: twcert.org.tw

Which versions are affected by CVE-2026-121816?

Herowatch Mini: all versions.Source: cve.now feed data

Am I affected, and how do I check?

The product entry lists Herowatch Mini with all versions from 0 onward. A separate condition names Herowatch Go App, all versions, as the affected product, so the listed product and condition do not match cleanly. The exposure depends on whether the device's ADB service is reachable from the attacker's side, which can be checked in the device's network and ADB settings.Source: twcert.org.tw

How do I fix CVE-2026-121816?

The checked facts list no fixed version, so no upgrade target can be named. Check the vendor's advisory for a fix before relying on any version change.Source: twcert.org.tw

What if there's no patch?

The checked facts give no workaround. The only condition stated is that the ADB service must be reachable, so limiting network access to that service is the step the facts point to, but they do not confirm it as an official fix.Source: twcert.org.tw