DEV Community

johnettagaweraks
johnettagaweraks

Posted on

The leaf CRL check that never runs in GoAhead

The leaf CRL check that never runs in GoAhead

Vulnerability overview

CVE-2026-115881 is a precise certificate-state failure in GoAhead's OpenSSL implementation. The server loads a CRL but does not set the OpenSSL verification flag that makes the list effective. An affected mutual TLS service accepts a revoked client certificate. EmbedThis assigns CVSS 3.1 score 9.1 and fixes the issue in GoAhead 6.1.1.

The affected versions are 3.4.5 through 6.1.0. The vendor maps the issue to CWE-295 and CWE-299. The first describes improper certificate validation; the second describes an improper check for certificate revocation.

Mechanism and exploitation conditions

The relevant setting is ME_GOAHEAD_SSL_REVOKE, which points to a PEM-encoded CRL. When the path is non-empty, GoAhead obtains the OpenSSL certificate store and calls X509_STORE_load_locations. A failed load aborts startup, so the file-loading operation is not the missing step.

The missing step is a call to enable X509_V_FLAG_CRL_CHECK. OpenSSL's verifier checks the flag before it evaluates revocation. If neither CRL checking nor OCSP checking is enabled, the revocation routine returns success without consulting the list. The certificate can be listed as revoked and still pass.

GoAhead's verification callback contains a default path that would reject X509_V_ERR_CERT_REVOKED, but the verifier never produces that error. A valid chain with a good signature and a revoked leaf can therefore look successful to the callback.

Exploitation requires the OpenSSL backend, ME_GOAHEAD_SSL_VERIFY_PEER=1, a configured CA bundle, ME_GOAHEAD_SSL_VERIFY_ISSUER=1, a non-empty CRL, and a revoked certificate from a trusted CA. The default build does not enable the first steps.

Impact

The attacker receives the access attached to the certificate identity. If the certificate represented a field device, a support account, or an administrator endpoint, the application may expose management routes or operations that the operator believed had been revoked.

The CVSS vector is network reachable, low complexity, no privileges, no user interaction, scope unchanged, with high confidentiality and integrity impact and no availability impact. It assumes the attacker already has the revoked certificate. The severity comes from the failure to enforce an expected access boundary.

Affected products and scope

The defect is in GoAhead's OpenSSL integration. Mbedtls builds use a different revocation path and the vendor says they are not vulnerable to this CVE. GoAhead appears in many embedded management systems, so the product build and certificate configuration are more useful than a bare product name.

The affected range is 3.4.5 through 6.1.0. Patching decisions should include the firmware version, the TLS backend, whether mutual TLS is required, the trusted CA bundle, issuer verification settings, and how the CRL is delivered and refreshed.

Exposure context

On November 18, 2026, ZoomEye returned 6,627,002 product-fingerprint matches for app="GoAhead" and 0 matches for the exact CVE query. Exposure uses the larger successful product count, but that count does not show backend or certificate settings.

The ZoomEye result should be treated as an inventory signal. It cannot establish that a device has a trusted CA bundle or a revoked client credential.

Remediation and mitigations

Install GoAhead 6.1.1 or later. The fixed code enables leaf-certificate CRL checking after the list loads. The vendor deliberately leaves chain-wide checking disabled because it requires CRLs for every issuer in the trust chain.

Until the fixed firmware is available, restrict access to the management service and review whether mutual TLS can be disabled safely. A network control can reduce reachability, but it does not repair the server's certificate decision.

Test the patch with a certificate that the managed CA has revoked. Check for a failed handshake and the expected verification error. Also test a valid certificate to ensure the update did not break normal client authentication. The meaningful result is that the loaded CRL now participates in verification.

References

Top comments (0)