Skip to main content
← Vulnerabilities

About Time Technologies|Herowatch Go - Security Misconfiguration

All versions of Herowatch Go App from About Time Technologies are affected. CVSS rates the flaw High at 8.5, and no fix is listed in the checked facts.

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

8.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected product is Herowatch Go App, all versions. The system signing uses a publicly available test key.

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, 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 30 if CISA's SSVC rates it automatable

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

Published
Last modified
Published
Not listed in CISA KEV
0.13% · 2nd percentile
20/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Herowatch Mini from About Time Technologies has a system signing flaw: a publicly available test key can be used to sign malicious programs. An attacker with low-privilege local access, meaning they must already be logged in, can use this to raise their privileges and run arbitrary code.

Read the original description

Herowatch Mini developed by About Time Technologies has a system signing vulnerability. Authenticated local attackers can exploit a publicly available test key to sign malicious programs, allowing them to elevate privileges and execute arbitrary code.

What to do

  • Check whether your setup matches what the bug needs.

    Affected product is Herowatch Go App, all versions. The system signing uses a publicly available test key.
  • Workaround: The checked facts list no fix and no workaround. No mitigation can be named from these sources, so the advisory's own guidance is the place to look for interim steps.

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 Go

    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-121818

Is CVE-2026-121818 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 system signing uses a publicly available test key, so the signature check does not protect against malicious programs. An attacker who uses that key can sign malicious programs, which could elevate privileges and execute arbitrary code.Source: twcert.org.tw

Which versions are affected by CVE-2026-121818?

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

Am I affected, and how do I check?

The advisory lists Herowatch Go App, all versions, with the version range starting at 0 and no upper limit. The checked facts do not describe a version command or setting for checking the installed build.Source: twcert.org.tw

How do I fix CVE-2026-121818?

The checked facts name no fixed version, so no upgrade target can be given from these sources. Check the About Time Technologies advisory for an update before relying on any version.Source: twcert.org.tw

What if there's no patch?

The checked facts list no fix and no workaround. No mitigation can be named from these sources, so the advisory's own guidance is the place to look for interim steps.Source: twcert.org.tw