# CVE-2026-77054: Cleartext Storage of Sensitive Information in boneIO


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-vr49-42jp-v28f

## What is CVE-2026-77054?

CVE-2026-77054 is a medium-severity vulnerability in boneIO, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-77054?


## How do I fix CVE-2026-77054?

No fix has been published for CVE-2026-77054 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77054 being exploited?

There is no known exploitation of CVE-2026-77054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77054 and fix it if it is affected.

What it is: CVE-2026-77054 is a medium-severity vulnerability in boneIO, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-77054 in the wild and no public exploit code.

Affected product: boneIO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77054/ (Markdown: https://insights.sbomify.com/CVE-2026-77054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77054
- OSV: https://osv.dev/vulnerability/CVE-2026-77054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77054/
Summaries are generated and may contain mistakes; the official description above is the record.