GoAhead TLS Vulnerability CVE-2026-115881: Three Flaws in the Web Server Inside IoT, Firewall and OT Devices
The GoAhead embedded web server had three TLS bugs, including CVE-2026-115881, which lets revoked client certificates keep working. GoAhead 6.1.1 fixes them. Here is who is exposed and what to ask your device makers.
Where Worldwide
On this page 7 sections
The GoAhead web server, which manufacturers build into the firmware of network gear, building controllers and industrial equipment, had three bugs in how it handles encrypted TLS connections. The worst, CVE-2026-115881, can let a device keep accepting a login certificate you have already revoked, so a security control you rely on can fail without telling you.
The maintainer has released GoAhead 6.1.1 to fix the bugs. Most businesses cannot install it themselves, though, because it reaches your devices only when the manufacturer ships a firmware update. Below we cover what is confirmed, what is only claimed, and what to do this week.
What happened with GoAhead
GoAhead is a compact web server that runs the admin page or API on many embedded devices. EmbedThis maintains it and published the advisories on GitHub. Sébastien Féry, a researcher at FoxIO, reported three TLS bugs in April 2026, one for each TLS library GoAhead can be built with. According to FoxIO's timeline:
- April 22, 2026: LibreSSL issue reported
- April 27, 2026: Mbed TLS issue reported
- April 30, 2026: OpenSSL issue reported
- August 2, 2026: GoAhead 6.1.1 released
- October 12, 2026: advisories published on GitHub
- October 26, 2026: FoxIO published its research
On October 27, 2026, the oss-security mailing list carried a summary of the three bugs.
The three GoAhead TLS flaws explained
Whether a device is affected depends on two things: which TLS library the manufacturer chose and how certificate checking is set up.
| Flaw | TLS library | Affected GoAhead versions | Severity | What it does |
|---|---|---|---|---|
| CVE-2026-115881 (GHSA-5m75-xq69-c3c5) | OpenSSL-compatible | 3.4.5 through 6.1.0 | Critical, CVSS 9.1 | The revocation list loads, but GoAhead never turns on revocation checking, so revoked client certificates are still accepted |
| CVE-2026-115884 (GHSA-r392-vqwx-3r4g) | LibreSSL 3.2.x and 3.3.2 to 3.3.6 | 6.1.0 and earlier | High, CVSS 7.4 | An over-long certificate chain gets past the depth limit and can log in as a client |
| No CVE (GHSA-fmvx-2xfx-2gq4) | Mbed TLS | 4.0.2 through 6.1.0 | Moderate, CVSS 5.9 | A one-character typo cuts a 2048-bit key exchange value down to 1 byte, so someone listening on the network may be able to decrypt TLS 1.2 sessions |
The vendor advisories list GoAhead 6.1.1 as the fix for all three.
What is confirmed and what is not
Confirmed by the vendor advisories and FoxIO's testing:
- FoxIO ran GoAhead 6.1.0 with OpenSSL 3.6.2, and a revoked client certificate still completed the handshake. The advisory notes that GoAhead gives no warning, so administrators have no sign that revocation is off.
- With LibreSSL 3.3.6, GoAhead 6.1.0 accepted a 17-certificate chain rooted in a certificate authority the attacker controlled. LibreSSL 4.3.1 rejected the same chain.
- On the Mbed TLS bug, FoxIO's proof of concept recovered the session secret after five attempts. It works only when the client accepts the broken key exchange. The OpenSSL client FoxIO tested refused it, and the advisory says most modern clients will too.
The exposure is narrower than the headline suggests. CVE-2026-115881 matters only when a device uses mutual TLS (client certificates) with a revocation list configured. The LibreSSL bug requires client certificate checking on with issuer checking off, and the advisory says default builds do not check client certificates at all. The Mbed TLS bug does not affect the default build, which uses OpenSSL, and it does not touch TLS 1.3 or ECDHE connections.
Claimed but not independently verified: FoxIO's own post says GoAhead is used in "hundreds of millions of IoT, Firewall, OT, and Military devices." It also names companies including D-Link, HP, Canon, Honeywell and Siemens as GoAhead users. Those figures are FoxIO's estimate. We could not verify them, and a brand appearing on that list does not mean any of its current products are vulnerable.
Not known: which device models and firmware versions contain an affected build, and which manufacturers have shipped 6.1.1. Neither FoxIO nor the advisories say whether these bugs have been exploited in the wild. FoxIO has published proof-of-concept code, so assume anyone interested can reproduce the bugs.
Why the GoAhead flaws matter for a business network
Certificate revocation is the step that ends access. Companies revoke a certificate when a technician leaves, a laptop goes missing or a contractor's job ends. If a building controller, firewall admin page or plant gateway quietly ignores the revocation list, that person or device keeps access, and nothing in your logs will look wrong.
It also takes a long time for a fix like this to reach the field. The patch has existed since August, but it only protects you once your manufacturer builds it into firmware and someone installs it. Devices that are past end of support may never get it.
What to do this week
| Step | How to do it |
|---|---|
| List devices with a web admin page | Include HVAC and building controllers, cameras, UPS and power units, printers, firewalls, and industrial gateways |
| Ask each manufacturer | Does the firmware use GoAhead? Which version and TLS library? When will an update with GoAhead 6.1.1 or later ship? |
| Check vendor advisories | Watch each manufacturer's security page for firmware updates mentioning GoAhead 6.1.1 |
| Do not rely on revocation alone | Until a device is patched, when access must end, also remove the account or trust entry on the device itself |
| Restrict management access | Keep admin interfaces off the internet and reachable only from a management network or VPN |
| Use fingerprinting | Security teams can use FoxIO's published JA4Scan fingerprints to spot GoAhead servers, and JA4S logs to spot DHE key exchange suites |
If you build firmware with GoAhead yourself, move to 6.1.1 or later. Also set VERIFY_ISSUER=1 with a trusted CA bundle when using mutual TLS, prefer OpenSSL or LibreSSL 4.x, and turn off finite-field DHE suites on Mbed TLS builds if you cannot upgrade right away. For help separating management networks, see our security hardening and self-hosting infrastructure services.
GoAhead TLS vulnerability questions people are asking
What is GoAhead?
GoAhead is an embedded web server that manufacturers put inside device firmware to run admin pages and APIs. EmbedThis maintains it.
What is CVE-2026-115881?
It is a critical GoAhead flaw (CVSS 9.1). On OpenSSL builds that use client certificates and a revocation list, GoAhead accepts revoked certificates. It affects versions 3.4.5 through 6.1.0.
Which GoAhead version fixes the TLS flaws?
GoAhead 6.1.1, released August 2, 2026, according to the vendor advisories and FoxIO.
Is the GoAhead vulnerability being exploited?
Neither FoxIO nor the advisories report attacks in the wild. Proof-of-concept code is public.
Can I update GoAhead on my device myself?
Usually not. GoAhead is built into the firmware, so you need a firmware update from the device manufacturer.
Does this affect my company website?
These bugs are in GoAhead's own code. Websites served by other web servers are not affected by these advisories, but any device on your network running GoAhead could be.
How do I know if a device uses GoAhead?
Ask the manufacturer or check its security advisories. Security teams can also scan with the JA4Scan fingerprints FoxIO published.
The bigger lesson
The worst bug here is a control that was loaded but never switched on. Nothing broke, and nothing logged an error. Security settings on embedded devices need testing, not just configuring, and every device on your network needs an owner who knows where its firmware updates come from and who installs them.
Want a second set of eyes on your devices and management networks? See security hardening or request a tech quote.
Get security alerts like this by email, plus our free checklist, at /security-alerts.
Sources: FoxIO: Choose Your Backend, Three TLS Bugs in GoAhead; GoAhead advisory GHSA-5m75-xq69-c3c5; GoAhead advisory GHSA-r392-vqwx-3r4g; GoAhead advisory GHSA-fmvx-2xfx-2gq4; oss-security: Three TLS Bugs in GoAhead.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Rosstat Cyberattack: Russia's Statistics Agency Is Still Restoring Systems, What Is Confirmed and What Businesses Should Check
Rosstat says it is still restoring systems after cyberattacks from October 29 to November 1, 2026. Hackers cla...
Ransomware Business Continuity: Why Backups Alone Won't Keep Your Company Running, and What to Do This Week
Backups can bring systems back, but they do not keep work moving during the outage. Here is what Japan's IPA l...
Healthcare Cold Storage Attack: Hackers Changed Freezer Settings at the French Blood Service, What Is Confirmed and What to Check
A cyberattack on a refrigeration contractor altered cold room settings at three French blood service sites. No...
