# CVE-2026-77058: Cross-Site Request Forgery (CSRF) in boneIO


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/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-xmrj-8287-w33q

## What is CVE-2026-77058?

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

### Official description

boneIO Black is vulnerable to Cross-Site Request Forgery (CSRF) on all state-changing API endpoints because it lacks CSRF tokens and does not validate Origin or Referer headers. A remote attacker can craft a malicious webpage that, when visited by a user on the internal network, sends cross-origin requests to the device. This allows the attacker to reboot the controller, toggle relay circuits, control gates and blinds, or shut down the device, causing loss of integrity and availability. Critically, due to CVE-2026-77053 (authentication disabled by default), any user on the same internal network can trigger attacker-controlled actions by visiting the malicious website.

This issue was fixed in version 1.6.0.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-77058 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77058 is a medium-severity vulnerability in boneIO, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-77058 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-77058/ (Markdown: https://insights.sbomify.com/CVE-2026-77058/index.md)
```

## Sources

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

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