> status: mostly fine. patch anyway.practical AI security · est. 2026

Calm down. · Both

Calm down: the "3 Critical" GoAhead TLS bugs are one Critical, and all three are opt-in

By alkizz ·

At 4:51 PM ET on Oct 26, John Althouse, founder and CTO of FoxIO, posted "Announcing 3 Critical vulns" in GoAhead, a web server device makers embed in their products, and followed it with a long list of big brand names. The post closes with "These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure." Calm down.

The post links to FoxIO's own blog, titled "Choose Your Backend: Three TLS Bugs in GoAhead," and its TLDR rates the bugs the way the vendor, Embedthis, does in its GitHub advisories: one Critical, one High and one Medium. The blog doesn't say three Criticals; only the post does.

Here they are, by the vendor's IDs:

None of that is on by default. The default build uses OpenSSL with mTLS off and no CRL, and the vendor puts it plainly: "The default GoAhead build does not enable mTLS and does not load a CRL." On the LibreSSL bug, it adds, "Mutual TLS is an opt-in feature. Default GoAhead builds do not perform any client-certificate verification and are not exposed to this defect." GoAhead 6.1.1 fixes all three. The release notes date it Aug 2, 2026, for device builders, and the advisories went public Oct 12, well before the blog went up Oct 26, but the post is right that device makers still have to ship firmware with the fix.

The vendor's advisories and FoxIO's blog cite CVE-2026-115881 and CVE-2026-115884, but both are only reserved at cve.org with no NVD record, and the Mbed TLS bug has no CVE at all, so ask vendors by SA ID.

Claimed vs. confirmed

What the post says What the sources say
"3 Critical vulns" One Critical (9.1), one High (7.4) and one Medium (5.9), per the vendor and FoxIO's blog
A '1-byte secret, "04"' FoxIO's blog lists eight possible values: "01, 02, 04, 08, 10, 20, 40 and 80"
DHE negotiation is "extremely likely" The vendor says OpenSSL 1.0.2 and later, current Go, current Java and mainstream browsers refuse the group and fall back to ECDHE, and FoxIO's own tested OpenSSL client rejected it
"LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS" Only on LibreSSL 3.2.x or 3.3.2–3.3.6 with issuer checking off, where self-signed certs "are already allowed," per FoxIO
The brand list FoxIO's blog TLDR carries the same list, and Althouse's follow-up post points to Embedthis's "Who's Using GoAhead" logo wall as the reference, which is marketing that doesn't even include Palo Alto Networks or Lockheed Martin. We found no public advisory for these bugs from any named vendor (Palo Alto Networks' advisory page has nothing on GoAhead)
Exploited? Not in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no exploitation reported by Embedthis, FoxIO, Blaze Labs, RuntimeWire or CISA

Embedthis's own page calls that wall "a small selection of who is using GoAhead," and it says nothing about what went into each product, which is the part that matters. As FoxIO's blog puts it, "Exposure depends on the TLS library and the verification settings built into the device." Nobody has confirmed that any named vendor ships an affected setup.

The internet mostly shrugged. As of about 10:37 PM ET on Oct 26, the post had about 16 reposts, 8 quotes and roughly 7.4K views. RuntimeWire added the qualifier the post skipped, that "the flaws affect particular TLS backends and configurations, not every device that includes GoAhead," and Blaze Labs, which reproduced the CRL bug on its own, put it plainly: "The attack also has substantial preconditions… That does not make it a generic unauthenticated bypass on every GoAhead build."

The bugs are real, though, and fixed. My take: the 9.1 is the one worth your time, but it's narrower than its score, because needing a revoked cert and its private key sits oddly with the vendor's CVSS rating of PR:N (no privileges required). It matters most if you revoke certs to cut off lost or decommissioned devices.

Classic security FUD. I've seen this exact play at least 25 times already (joking): real bugs, a scary headline, and a brand list doing the heavy lifting.

What to do:

Sources

Related

More briefs

← All briefs