An issue was discovered on Athom Homey and Homey Pro devices before 5.0.0.

published 2021-03-09 5y ago modified 2026-06-17 4mo ago also EUVD-2020-21338

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits: 0; none known

An issue was discovered on Athom Homey and Homey Pro devices before 5.0.0. ZigBee hub devices should generate a unique Standard Network Key that is then exchanged with all enrolled devices so that all inter-device communication is encrypted. However, the cited Athom products use another widely known key that is designed for testing purposes: "01030507090b0d0f00020406080a0c0d" (the decimal equivalent of 1 3 5 7 9 11 13 15 0 2 4 6 8 10 12 13), which is human generated and static across all issued devices.

Patch / fix

fixed in 2

homey homey_firmware 5.0.0
homey homey_pro_firmware 5.0.0

Is CVE-2020-28952 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-798 Use of Hard-coded Credentials

References

developer.athom.com /firmware
release-notes, vendor-advisory
homey.app /en-us/
product, vendor-advisory
yougottahackthat.com /blog/1260/athom-homey-security-static-and-well-known-keys-cve-2020-28952
third-party-advisory

Sources

CVE List CVE-2020-28952
NVD CVE-2020-28952

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.