Skip to main content
VulnerabilityPublished

CVE-2026-77061: boneIO Black directly excludes several API endpoints from the authentication

Source GCVE Database

0
Authoritative record:CVE-2026-77061· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.6.0 when convenient.

Data as of 26 Oct 2026, 16:36 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.6.0
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
boneIOboneioAffected
  • >=1.2.0 <1.6.0
Fixed in
  • 1.6.0
GitHubboneiopkg:github/boneioOther threatsAffected
  • >=1.2.0 <1.6.0
Fixed in
  • 1.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability has been fixed in boneIO Black version 1.6.0. Users should upgrade to version 1.6.0 or later to ensure all API routes require authentication, the interactive API documentation is disabled, and sensitive information such as the serial number is protected from anonymous access.

Description

boneIO Black had a vulnerability where several API endpoints were excluded from authentication, allowing unauthenticated remote attackers on the local network to access sensitive information such as system logs, firmware version, serial number, MQTT username, configuration file listings, and API documentation. This information could facilitate reconnaissance and targeted attacks. The issue was fixed in version 1.6.0 by requiring authentication for all API routes, disabling interactive API documentation, and withholding the serial number from anonymous users.

References

Community reviews

Loading reviews…