boneIO Black is vulnerable to Cross-Site Request Forgery (CSRF) on all state-changing API endpoints because it lacks
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.6.0 when convenient.
Data as of 26 Oct 2026, 16:35 UTC
- Patch
- Available – fixed in 1.6.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/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 Black to version 1.6.0 or later, where this CSRF vulnerability has been fixed. The fix includes implementing CSRF tokens and validating Origin or Referer headers to prevent unauthorized cross-origin requests. No additional mitigation is required if the device is updated.
Description
boneIO Black suffers from a Cross-Site Request Forgery (CSRF) vulnerability affecting all state-changing API endpoints due to the absence of CSRF tokens and lack of Origin or Referer header validation. An attacker on the same internal network can exploit this by luring a user to a malicious webpage, causing unauthorized actions such as rebooting the controller or toggling relay circuits. This vulnerability leads to loss of integrity and availability of the device. The issue is resolved in version 1.6.0.