Cybersecurity firm FoxIO has disclosed three vulnerabilities in GoAhead’s handling of TLS. They could keep revoked client certificates working, let eavesdroppers decrypt some traffic, or help attackers get around a cap on certificate chain length.
GoAhead, a lightweight web server made by EmbedThis, runs the management interfaces of networking equipment, printers and industrial systems. According to FoxIO, it is present on hundreds of millions of devices across the IoT, OT, firewall and military sectors.
FoxIO’s Sébastien Féry, who documented the flaws this week, said each one affects only a subset of deployments. Which GoAhead devices are at risk depends on the TLS library the manufacturer built into the firmware and how it configured certificate checks.
The critical flaw, CVE-2026-115881 (CVSS score of 9.1), impacts GoAhead 3.4.5 through 6.1.0 when built with OpenSSL or a compatible library and configured for mutual TLS (mTLS) with a certificate revocation list (CRL). The server reads the list but never tells OpenSSL to consult it.
On these builds, a certificate an administrator has revoked, such as one tied to a stolen or compromised device, is still accepted, even with issuer verification switched on. Nothing at startup warns that revocation checks are inactive.
The eavesdropping risk comes from the second bug (CVSS score of 5.9, no CVE), found in GoAhead 4.0.2 through 6.1.0 builds that use Mbed TLS. A coding error weakens the encryption of some TLS 1.2 connections enough that recorded sessions can be decrypted offline, but only if the client accepts the flawed parameters.
The chain-length bypass, CVE-2026-115884 (CVSS score of 7.4), affects GoAhead up to version 6.1.0 built with LibreSSL 3.2.x or 3.3.2 through 3.3.6. It only works against servers that require client certificates but accept them from any issuer, so the length cap is the only safeguard attackers get past.
“None of these defects prevents the affected handshake from completing,” Féry wrote.
GoAhead 6.1.1, released on Aug 2, resolves the OpenSSL and Mbed TLS issues, and advisories for all three flaws were published on Oct 12. Mbed TLS builds can also be protected by turning off finite-field DHE cipher suites or moving to the OpenSSL backend.
For the LibreSSL issue, FoxIO recommends enabling issuer verification with a trusted CA bundle, or switching to OpenSSL or LibreSSL 4.x.
The firm has also released proof-of-concept code and fingerprints that defenders can use to spot internet-facing GoAhead servers and determine which TLS library they rely on.
In a post on X, FoxIO founder and CTO John Althouse named Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin and Boeing among the companies whose devices rely on GoAhead. FoxIO has not specified whether any of their products use a vulnerable configuration.
Althouse cautioned that the availability of an upstream fix “doesn’t mean there’s a patch available for the devices yet — that’s up to the manufacturer.”
Related: CISA Warns of Node2Shell Exploitation as Honeypots Log Attack Attempts
Related: PHP2Shell Exploitation Moves From Probes to Working Shells
Related: Tailscale Rushes Patches After Uncoordinated Disclosure of ‘Tailworm’ Flaws
