Quick answers
- Is CVE-2026-77057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77057 being exploited in the wild.
- How severe is CVE-2026-77057?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- boneIO Black before 1.6.0.
- Is there a fix for CVE-2026-77057?
- Yes: fixed in 1.6.0. Until then: Restrict network access to the web interface (port 8443) and SSH service to trusted networks only using a firewall or access control rules. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77057 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-77057?
- Check whether you run boneIO Black at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.0
Restrict network access to the web interface (port 8443) and SSH service to trusted networks only using a firewall or access control rules.
Technical details
The vulnerability consists of two separate weaknesses: the POST /api/login endpoint on the web interface and the SSH service lack rate-limiting on authentication attempts, and password complexity is not enforced. An unauthenticated remote attacker can perform brute-force attacks over the network without restriction; the fix (version 1.6.0) adds per-source and per-account rate-limiting on web logins, enforces 8-character minimum passwords, and limits SSH to three attempts per connection.
Affected products
- boneIO Black before 1.6.0
Timeline
- 2026-10-26: disclosed