Critical GoAhead Vulnerability Lets Attackers Authenticate Using Revoked Certificates

A critical vulnerability in GoAhead’s OpenSSL integration lets attackers with revoked client credentials complete mutual TLS authentication and retain access tied to those identities.

Tracked as CVE-2026-115881 and GOAHEAD-SA-2026-0006, the flaw carries a CVSS score of 9.1 and affects GoAhead versions 3.4.5 through 6.1.0. Version 6.1.1 fixes the issue.

Researcher Sébastien Féry reported the vulnerability, which affects explicitly configured deployments rather than GoAhead’s default installation.

Critical GoAhead Vulnerability

Successful exploitation requires an OpenSSL-compatible backend, enabled client-certificate authentication, a trusted certificate authority bundle, issuer verification, and a configured Certificate Revocation List, or CRL. The attacker must possess a previously trusted certificate listed as revoked.

The defect resides in sslOpen() within src/openssl.c. GoAhead successfully loads the configured CRL into OpenSSL’s certificate store using X509_STORE_load_locations(), but never enables the X509_V_FLAG_CRL_CHECK flag required to enforce revocation checking.

Consequently, when neither CRL nor OCSP checking is enabled, OpenSSL’s revocation verification routine returns success without consulting the loaded list.

Foxio stated that because the CRL loads successfully, administrators receive no startup warning that their configured revocation policy is ineffective.

The certificate verification callback would reject X509_V_ERR_CERT_REVOKED, identified as error 23. However, the missing flag prevents the verifier from generating that error.

A supplied verification trace instead showed successful validation throughout the certificate chain, allowing the revoked identity to complete authentication.

This creates a security gap for stolen, compromised, or decommissioned device credentials. Revoking such certificates does not remove their access on affected deployments, even when issuer verification remains enabled.

OpenSSL-compatible libraries share the relevant API requirement; GoAhead’s separate Mbed TLS revocation path is unaffected by this particular defect.

The same security release addresses GOAHEAD-SA-2026-0005, a separate Mbed TLS integration vulnerability involving truncated Diffie-Hellman parameters.

GoAhead supplied a one-byte modulus instead of the intended 2048-bit value, undermining session confidentiality when clients accepted the malformed parameters.

Another issue, GOAHEAD-SA-2026-0004, permits certificate chains exceeding the configured depth limit on certain LibreSSL releases when VERIFY_ISSUER=0. This bypass concerns chain-depth enforcement rather than establishing trust in an otherwise untrusted certificate authority.

These findings demonstrate that exposure depends on the selected TLS backend and verification settings. They should not be interpreted as evidence that every device embedding GoAhead is vulnerable to all three flaws.

Embedthis identifies GoAhead 6.1.1 as the patched release. The CRL fix explicitly calls X509_STORE_set_flags(store, X509_V_FLAG_CRL_CHECK) after loading the revocation list, restoring leaf-certificate revocation enforcement without requiring new configuration options.

Device manufacturers and administrators should rebuild and redeploy affected installations, prioritizing systems using mutual TLS.

Post-upgrade validation should confirm that revoked client certificates fail authentication, rather than relying solely on successful CRL loading or clean startup logs.

Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team 

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories