GoAhead 6.1.0 OpenSSL Builds Accept Revoked Client Certificates Despite Loaded CRL

The primary defect, tracked as CVE-2026-115881 and rated 9.1 by EmbedThis, occurs only when the OpenSSL backend is selected, client certificates are required, issuer checking is enabled, and a revocation list is explicitly configured. FoxIO testing against 6.1.0 with OpenSSL 3.6.2 confirmed a revoked certificate was accepted without error. The Mbed TLS backend uses a separate code path and is unaffected. Two additional issues affect LibreSSL legacy verifier builds and Mbed TLS finite-field DHE key exchange, the latter permitting passive decryption when weak clients accept a 1-byte DH value.

Procurement records and device firmware analyses show GoAhead embedded in routers, industrial gateways, and network appliances at scale. The configuration required for exploitation matches deliberate operator choices for mutual authentication rather than default settings. Official statements from EmbedThis emphasize the fix in 6.1.1 released August 2026, yet the advisory omits any interim mitigation beyond upgrade, leaving long-lifecycle devices exposed.

Independent verification of the three CVEs remains pending in NVD as of late October 2026. The pattern of silent failure on revocation mirrors prior TLS library misconfigurations documented in OpenSSL advisories and FIPS validation reports. Operators relying on certificate lifecycle management for device fleets face integrity and confidentiality risks until patches propagate through firmware supply chains.

Next steps include firmware audits of deployed GoAhead instances and verification that post-6.1.1 builds actually invoke X509_STORE_CTX_set_flags with CRL checking enabled. Continued monitoring of EmbedThis contract awards will indicate whether downstream vendors adopt the corrected library.