GoAhead 6.1.1 Fixes Three TLS Flaws in Device Server

Device makers that build on the GoAhead embedded web server have a fix for three flaws in how it handles encrypted connections, and network defenders now have a way to spot exposed builds. Version 6.1.1 corrects all three, according to security advisories from GoAhead’s maintainer, Embedthis, published on 12 October. Security firm FoxIO, which found the bugs, followed on 26 October with a technical write-up that includes scan fingerprints for each TLS library GoAhead can use.

The worst flaw, CVE-2026-115881, is rated critical at 9.1 out of 10. It means a GoAhead server set up to check client certificates against a revocation list will still let a revoked certificate in. The other two can leave a chain-length limit unenforced or let an eavesdropper decrypt some sessions. Which, if any, apply depends on how each device was built. No source reports that any of them has been exploited.

In brief

GoAhead 6.1.1, given to device builders on 2 August and published with advisories on 12 October, fixes three TLS bugs found by FoxIO.
The critical bug lets revoked client certificates connect on OpenSSL builds that use certificate revocation lists.
FoxIO has published fingerprints that tell defenders which TLS library a GoAhead server is using, and so which bug may apply.

Three bugs, three TLS libraries

GoAhead is a small web server built into devices so they can be managed through a browser. FoxIO says it runs on routers, switches, printers, gateways and industrial controls, and claims it is used in “hundreds of millions” of devices, naming makers such as Palo Alto Networks, D-Link, HP, Canon, Siemens and Boeing. GoAhead can use OpenSSL, the default, or Mbed TLS, and the OpenSSL path also works with LibreSSL.

The critical flaw affects OpenSSL builds from version 3.4.5 to 6.1.0. GoAhead loaded the revocation list but never switched on OpenSSL’s revocation check, so the list was ignored, and the server gave no warning at startup. FoxIO showed a revoked certificate completing a connection on GoAhead 6.1.0 with OpenSSL 3.6.2. It only matters where a device requires client certificates and has a revocation list configured, which is not the default build.

The second flaw, CVE-2026-115884, is rated high at 7.4. On LibreSSL 3.2.x and 3.3.2 to 3.3.6, with client certificates required but issuer checking off, an over-long certificate chain was accepted. FoxIO’s 17-certificate chain from a self-made authority reached a protected page. OpenSSL, BoringSSL, AWS-LC and LibreSSL 4.x builds are not exposed.

The third, rated medium at 5.9 and without a CVE, is a typo in GoAhead’s Mbed TLS code, present since GoAhead 4.0.2 and dating from 2018, FoxIO says. It passed the wrong buffer length, shrinking a 2,048-bit key-exchange number to one byte. That leaves just eight possible shared secrets; FoxIO recovered the right one in five tries. It only affects older TLS 1.2 key exchanges with a client that accepts the broken numbers. FoxIO says the OpenSSL client it tested refused them, and TLS 1.3 is unaffected.

Fingerprints make the fix findable

The most useful part of FoxIO’s post for defenders is the scan data. It lists JA4Scan-TLS fingerprints for GoAhead 6.1.x on four libraries. These include OpenSSL 3.6.2 (03100h0s00sn_1fe27f6025fb_d06dc4648d2f_sr00ss537461), LibreSSL 3.3.6 (03100h0s00s0_9d52559f55bc_c64486648d2f_sr00sc24603c) and mbedTLS 3.6.6 (23100h0s01s0_d7d3025021f4_0475c5cede0d_sr0ss02265cf). For the Mbed TLS bug, it says a passive JA4S value such as t120100_009f_1ca028f07214 in logs suggests the vulnerable key exchange is in use. Since each bug is tied to a library, a scan that names the library narrows down which fix a device needs. Devices on other library versions may fingerprint differently.

The common thread is that “none of these defects prevents the affected handshake from completing”, in FoxIO’s words. Each failure looks like success. Revocation is a familiar weak point: when eMudhra’s intermediate keys were compromised, browsers moved within hours, but software that ignores revocation data stayed exposed. Client certificates have their own risks too, as a crafted certificate used against Vercel Sandbox showed this month.

The slow part is the supply chain. Embedthis says in its v6.1.1 release notes that the version went to device builders on 2 August, with advisories published on 12 October. Most owners cannot install GoAhead directly; they need a firmware update from the vendor. That makes this unlike a Tailscale client patch or a Node.js and Envoy update that users apply themselves.

What to do

Embedthis says upgrading “is recommended for all deployments”. The release resolves eleven advisories in total, including an authentication bypass, plus 31 further defects found in an internal audit. It says no critical or high finding remains open.

Where an upgrade is not yet possible, FoxIO’s advice depends on the library. For Mbed TLS, turn off the older finite-field key exchange or switch to OpenSSL. For LibreSSL, turn on issuer checking with a trusted CA bundle, which the chain-depth advisory says removes the exposure, or move to OpenSSL or LibreSSL 4.x. For the OpenSSL revocation bug, FoxIO lists no workaround, only the upgrade. FoxIO has posted proof-of-concept code, so the fair test now is how quickly vendors push 6.1.1 into their firmware.