# CVE-2026-77055: Improper Privilege Assignment in boneIO


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-qc57-j976-j85m

## What is CVE-2026-77055?

CVE-2026-77055 is a critical vulnerability in boneIO black_debian_images, published on 26 Oct 2026. 

### Official description

boneIO black_debian_images gives the boneio service account excessive privileges, including full passwordless sudo access and membership in the docker group. A local attacker who compromises the boneio user can use these privileges to escalate to root.

This issue was fixed in version 1.6.0: the image removes the sudoers rule and the docker group membership when it is sealed, and devices already in the field have both removed by migrations shipped with boneio 1.6.0 and applied on first start after the upgrade. Privileged operations now go through helpers that accept only a fixed set of commands, with migrations verified against Ed25519 signatures.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-77055 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: boneIO black_debian_images. 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-77055/ (Markdown: https://insights.sbomify.com/CVE-2026-77055/index.md)
```

## Sources

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

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