Particle.news

GoAhead TLS Flaws Exposed, Upstream Patch Available

Upstream fixes are ready — devices require manufacturer firmware updates before they are secured.

Overview

  • Security firm FoxIO publicly described three separate TLS defects in GoAhead in a write-up published Monday that include accepting revoked client certificates, enabling offline decryption of some TLS 1.2 sessions, and bypassing a certificate-chain length cap.
  • The most severe bug, tracked as CVE-2026-115881, affects GoAhead builds that use the OpenSSL backend with mutual TLS and a configured CRL because the server loads a revocation list but never enables revocation checking.
  • A Mbed TLS build error sends a one-byte Diffie-Hellman value instead of a full key so some clients can accept weak parameters and allow passive observers to decrypt recorded TLS 1.2 sessions, and older LibreSSL builds can accept over-long certificate chains when issuer checks are off (CVE-2026-115884).
  • EmbedThis released GoAhead 6.1.1 to device makers on August 2 and publicly posted the fixes on October 12, FoxIO published proof-of-concept code and fingerprints, and there have been no confirmed in-the-wild exploits as of late October.
  • Because the TLS backend and checks are chosen at firmware compile time, owners must rely on manufacturers to rebuild and ship firmware updates; defenders can use FoxIO’s fingerprints, disable vulnerable cipher suites, enable issuer checks, and rotate affected credentials to reduce risk.