GoAhead TLS Flaw Lets Revoked Client Certificates Authenticate

· Original article ↗

Summary

CVE-2026-115881 lets revoked client certificates authenticate in affected GoAhead versions with a specific OpenSSL-compatible mutual TLS and CRL configuration. GoAhead 6.1.1 fixes the flaw; no in-the-wild exploitation is reported.

Key points

  • The flaw affects GoAhead 3.4.5–6.1.0 when using the OpenSSL-compatible TLS backend with mutual TLS and a configured CRL.
  • GoAhead loads the CRL but does not enable OpenSSL’s X509_V_FLAG_CRL_CHECK, so a revoked certificate may still authenticate.
  • FoxIO reproduced the issue using GoAhead 6.1.0 and OpenSSL 3.6.2; the server gave no startup warning that revocation checking was ineffective.
  • An attacker would need a certificate issued by a trusted authority that was later revoked, plus its associated private key; this is not a generic authentication bypass.
  • GoAhead 6.1.1 fixes the issue. Embedded-device owners may need a firmware update from the device manufacturer.
  • The article reports no known in-the-wild exploitation as of October 28, 2026. JA4Scan fingerprints can aid discovery but do not prove a device is vulnerable.

Article Details

Vulnerability Types
  • Improper certificate revocation validation in mutual TLS
Severity
Critical (CVSS 9.1)
Affected Versions
  • GoAhead 3.4.5 through 6.1.0, when using the OpenSSL-compatible TLS backend with a CRL configured
Exploitation Status
not_reported
Exploit Availability
public_poc
Patch Status
available
Workarounds
  • Restrict management interfaces to trusted networks, a VPN, or a dedicated administrative segment.
  • Verify revocation enforcement using a dedicated test certificate.
  • Review and revoke or replace affected credentials.

CVE

Vendors

Products

Tools

Industries

Related Articles