GoAhead TLS Flaws Permit Revoked Certificates and Expose Sessions to Decryption

Three backend-specific TLS vulnerabilities in GoAhead, an embedded web server deployed across hundreds of millions of devices, can undermine client authentication or session confidentiality under particular configurations. The most severe, CVE-2026-115881 (CVSS 9.1), affects OpenSSL-compatible builds of GoAhead 3.4.5–6.1.0 with mutual TLS and a certificate revocation list configured: revoked client certificates remain accepted even when issuer verification is enabled. A legacy LibreSSL flaw (CVSS 7.4) permits certificate chains exceeding the configured depth limit when client certificates are required but issuer verification is disabled. An Mbed TLS flaw (CVSS 5.9), affecting GoAhead 4.0.2–6.1.0, truncates a 2048-bit Diffie-Hellman modulus to one byte, making TLS 1.2 DHE_RSA sessions recoverable by an observer if the client accepts the malformed parameters.

GoAhead 6.1.1 is the remediation release, and device manufacturers must integrate it into firmware updates before downstream users benefit. Organizations should inventory GoAhead-based management interfaces and confirm the compiled TLS backend, authentication settings, and vendor patch availability rather than assume every deployment is affected. Interim measures include disabling finite-field DHE cipher suites for affected Mbed TLS builds and enabling issuer verification with a trusted CA bundle or moving to OpenSSL or LibreSSL 4.x for affected legacy LibreSSL deployments. The release also addresses a password-validation bypass involving Blowfish-stored passwords. FoxIO has published proof-of-concept code, but no exploitation was reported as of October 27, 2026; the number of affected devices and manufacturers’ deployment status remain unknown.