GoAhead 6.1.1 addresses revoked certificate and TLS session risks
EmbedThis has released GoAhead 6.1.1, addressing three TLS issues in the embedded web server used in firmware for management interfaces on routers, printers, gateways and industrial controllers. The most serious issue, CVE-2026-115881, has a vendor rating of 9.1 and can allow a revoked client certificate to authenticate on affected OpenSSL mutual-TLS deployments.
GoAhead 6.1.1 was released to device makers on August 2, 2026 and publicly published on October 12. The issues were described by Sébastien Féry of FoxIO on October 26. EmbedThis says GoAhead runs in hundreds of millions of devices, although the population of devices using an affected TLS backend and configuration has not been established.
Revocation list loaded but not enforced
The OpenSSL issue affects GoAhead versions 3.4.5 through 6.1.0 where mutual TLS is enabled, client certificates are required, issuer checking is enabled and a certificate revocation list is configured. GoAhead loads the revocation list at startup without reporting an error, but does not enable revocation checking in the relevant TLS path.
As a result, a client holding a certificate signed by a trusted authority can complete authentication even if that certificate is on the configured revocation list. This could include a certificate associated with a stolen or retired device. FoxIO tested the condition against GoAhead 6.1.0 with OpenSSL 3.6.2 and issuer checking enabled.
Builds using the Mbed TLS backend are not affected by CVE-2026-115881 because that backend uses a separate revocation-checking path. The advisory does not list an interim mitigation for affected OpenSSL builds; the specified remediation is an upgrade to GoAhead 6.1.1.
Two additional backend-specific TLS fixes
A separate LibreSSL legacy-verifier issue affects GoAhead 6.1.0 and earlier when linked with LibreSSL 3.2.x or 3.3.2 through 3.3.6. Where client certificates are required but issuer checking is disabled, an over-long certificate chain can still be accepted as an authenticated client. EmbedThis identifies the flaw as CVE-2026-115884 and rates it 7.4.
Organizations unable to update that LibreSSL configuration can enable issuer checking with a trusted CA bundle, or use OpenSSL or LibreSSL 4.x. OpenSSL, BoringSSL, AWS-LC and LibreSSL 4.x reject the over-long chain described in the advisory.
The third TLS issue affects GoAhead 4.0.2 through 6.1.0 with the Mbed TLS backend. A length typo can send a one-byte Diffie-Hellman value rather than the intended 2048-bit value during finite-field DHE key exchange. If a client accepts the exchange, a passive observer who recorded traffic can derive the session key and decrypt the session.
OpenSSL, current Go and Java implementations, and mainstream browsers reject the undersized value and fall back to a stronger key exchange, preventing the session from completing through that path. TLS 1.3 and ECDHE sessions are unaffected, and Mbed TLS 4.x removed the finite-field exchange involved. EmbedThis recommends upgrading, disabling finite-field DHE suites, or using the OpenSSL backend.
Firmware delivery determines exposure
The TLS backend and its settings are chosen when device firmware is compiled, so owners generally cannot determine exposure from outside a device. GoAhead 6.1.1 is a drop-in replacement for manufacturers to rebuild into firmware and distribute as an update. As of October 27, no reported attacks had used these flaws, and no manufacturer had been shown to ship an affected backend and configuration.
The same release resolves 11 advisories, including a login bypass involving HTTP Basic or form login and passwords stored in GoAhead's newer Blowfish format. After upgrading, EmbedThis recommends ending active sessions, restarting the server and changing Blowfish-stored passwords. Businesses should inventory products that may embed GoAhead, request firmware status from suppliers, verify TLS backend choices where possible, and prioritise updates to version 6.1.1 when vendors make them available.