Was Clock Hacked?

No Publicly Reported Incidents. As of April 2026, Clock has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates Clock's security posture as adequate (security dimension score: 70/100). Trust Score: 67/100 (B-). Last checked: 2026-04-17.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score67/100 (B-)
Security Dimension70/100
PublisherSamsung Electronics Co., Ltd.
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see Clock Trust Score on Nerq.

FAQ

Has Clock been hacked?
As of April 2026, Clock has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does Clock have?
Clock has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is Clock safe to use after a breach?
With no reported breaches, Clock appears safe based on available data.
Where can I check Clock's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for Clock. View the full trust analysis at nerq.ai/safe/com-sec-android-app-clockpackage.

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy