CVE-2026-77054: boneIO · Cleartext Storage of Sensitive Information
Affects boneIOSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.6.0 when convenient.
Data as of 26 Oct 2026, 17:30 UTC
- Patch
- Available – fixed in 1.6.0
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade boneIO and boneio to 1.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| boneIOboneio | Affected
| Fixed in
|
GitHubboneiopkg:github/boneioOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade boneIO to version 1.6.0 or later, where passwords are properly hashed or stored securely with restricted file permissions, and secret values are no longer exposed via the API or logs. This version fixes the cleartext storage and exposure issues. No additional mitigation is required if running version 1.6.0 or later.
Description
boneIO Black stores passwords, including the MQTT broker and web panel passwords, in cleartext. The GET /api/config endpoint returns the full configuration with sub-services passwords exposed. Any authenticated user can call the endpoint and access the administrative passwords in cleartext form. Critically, due to CVE-2026-77053 (authentication disabled by default), an unauthenticated attacker on the same local network can retrieve all passwords. This issue was fixed in version 1.6.0: web panel passwords are stored as salted scrypt hashes in a file readable only by the service account, and the API and logs no longer return secret values. The MQTT broker password has to stay recoverable because the application presents it to the broker as a client; it is kept in a separate file readable only by the service account and is no longer exposed through the API.