GoAhead TLS Flaws: Revoked Certificate Acceptance, Chain-Depth Bypass, and Weak DHE
1. Basic Information
- Title: Choose your backend: three TLS bugs in GoAhead
- Source: FoxIO
- Date: 2026-10-26
- Original: FoxIO
- Related Sources: SecurityWeek: TLS Flaws Found in GoAhead Web Server, GHSA-5m75-xq69-c3c5, GHSA-r392-vqwx-3r4g, GHSA-fmvx-2xfx-2gq4, GoAhead v6.1.1
- Related Malware: None specified
- Related Threat Actors: None specified
- Related CVEs: CVE-2026-115881, CVE-2026-115884
- Related Products: GoAhead 3.4.5 through 6.1.0, OpenSSL, LibreSSL, Mbed TLS
- Severity: High
2. Executive Summary
FoxIO has reported three TLS implementation flaws in the embedded web server GoAhead, affecting different TLS backends: OpenSSL, LibreSSL, and Mbed TLS. These include the failure to enforce Certificate Revocation Lists (CRLs) (CVE-2026-115881), the bypass of certificate chain depth verification (CVE-2026-115884), and a DHE weakening issue where a 2048-bit DH modulus is treated as 1 byte. All of these issues have been addressed in GoAhead 6.1.1.
Because the TLS client authentication and communication confidentiality of web servers widely used in embedded devices can be disabled depending on the build-time TLS backend and configuration, organizations should check the impact on individual product firmware.
3. Attack Flow
Below are three independent paths with different TLS backends and configuration conditions, rather than a sequential three-step attack.
| Target Backend / Identifier | Attacker Action / Technique | Protocol / Presented Data Used | Defensive Indicators (Conditions / Artifacts) |
| --- | --- | --- | --- |
| OpenSSL-compatible backend (CVE-2026-115881) | Attempt mTLS connection using a revoked client certificate | TLS handshake (revoked client certificate) | In GoAhead 3.4.5 to 6.1.0, when mTLS and CRL are used, CRL checks are not enforced even if a CRL is loaded, allowing authentication to succeed |
| LibreSSL backend (CVE-2026-115884) | Create and present a certificate chain containing intermediate CAs that exceed the allowed depth | TLS handshake (certificate chain exceeding allowed depth) | Occurs in GoAhead through 6.1.0 with LibreSSL 3.2.x or 3.3.2 through 3.3.6, under the VERIFY_PEER=1 and VERIFY_ISSUER=0 configuration, where the chain is accepted |
| Mbed TLS backend (GHSA-fmvx-2xfx-2gq4) | Observe or interfere with TLS 1.2 DHE_RSA handshakes, exploit the 1-byte DH modulus to recover the shared secret and decrypt traffic | Passive observation or man-in-the-middle interference of TLS 1.2 DHE_RSA traffic | Occurs in GoAhead 4.0.2 to 6.1.0 with the Mbed TLS backend when the client accepts overly short DH parameters |
mTLS Revocation Bypass
1. The attacker possesses a revoked client certificate and its corresponding private key.
2. The attacker establishes an mTLS connection to a GoAhead server using an OpenSSL-compatible backend configured with a CRL.
3. Due to CVE-2026-115881, even though the CRL file is loaded, the revocation verification flag is not enforced, allowing authentication with the revoked certificate to succeed.
LibreSSL Chain Depth Bypass
1. The attacker creates a certificate chain that exceeds the configured allowed depth.
2. The attacker presents the chain to GoAhead running on a specific LibreSSL version and verification configuration (VERIFY_PEER=1 and VERIFY_ISSUER=0).
3. Due to CVE-2026-115884, the certificate chain violating the depth limit is accepted as is.
Mbed TLS DHE Weakening
1. The attacker observes or interferes with TLS 1.2 DHE_RSA handshakes on the network.
2. Due to a length specification error on the GoAhead side, a 1-byte DH modulus is utilized, making it easier to calculate the shared secret.
3. If the connecting client accepts sessions containing such extremely short DH parameters, communication traffic may be decrypted.
4. Attacker Positioning and Execution Location
- Positioned externally or internally with network access to the management interface of the target device, or located along the network path where TLS communication can be observed or interfered with.
5. Victim and Administrator Perspectives
Victims
- Connections appear completely normal, and explicit warnings may not appear in the browser or client.
Administrators
- May observe successful mTLS authentication using a revoked client certificate, the acceptance of certificate chains with unexpected depths, or negotiation of the TLS 1.2 DHE_RSA cipher suite.
6. Success and Failure Conditions
Success Conditions
- The target must be running an affected GoAhead version combined with a vulnerable TLS backend and configuration.
- For DHE weakening, the conditions are met when negotiating TLS 1.2 DHE_RSA and the client accepts overly short DH parameters. ECDHE, TLS 1.3, and Mbed TLS 4.x with DHE cipher suites removed are not subject to this path.
Failure Conditions and Mitigations
- Update to GoAhead 6.1.1 or the patched firmware provided by the product vendor.
- Isolate management interfaces at the network level, avoiding reliance solely on mTLS by combining multi-layer authentication and network allowlists.
- For DHE weakening, mitigations include disabling finite field DHE cipher suites, migrating to TLS 1.3, or switching to an unaffected backend. However, migrating to TLS 1.3 alone does not fix GoAhead's CRL-enforcement flaw in OpenSSL-compatible builds or its chain-depth verification flaw with the affected LibreSSL verifier.
7. What Happens Upon Success
- Client authentication bypass using revoked certificates, circumvention of certificate chain policies, or reduction in the confidentiality of TLS 1.2 sessions occurs.
- However, actual impact depends on each product's build configuration and runtime settings, so the mere use of GoAhead does not automatically confirm vulnerability.
8. Observable Logs
Inference: The following are potential logs to check within your organization. Their availability depends on log collection, retention, and product support, and they are distinct from observation records from threat intelligence sources.
- Email: None available
- Proxy / SWG / DNS: Check the client certificate subject, serial number, revocation status, and certificate chain depth in TLS handshakes.
- Endpoint / EDR: None available
- Identity / IdP: Check the history of administrative logins and configuration operations that occurred after successful mTLS authentication.
- SaaS / Cloud: Check audit logs of the device management interface and version information of firmware components.
- Network: Check for TLS 1.2 DHE_RSA negotiation or the presentation of unusual certificate chains.
9. Attack Success Assessment
- Attack Attempt Observed (Success Unconfirmed) (contact_only): Criteria: TLS handshake attempts or detection of vulnerable versions do not indicate successful authentication bypass or traffic decryption. Target: Device management surface
- Malware Execution or Authentication Success Confirmed (malware_or_authentication_success): Criteria: Confirm evidence that an authentication session was established using a revoked certificate or a policy-violating certificate chain. Target: mTLS session
- Data Theft or Session Compromise Confirmed (data_or_session_compromise): Criteria: For the Mbed TLS backend case, independently corroborate actually decrypted application data with the corresponding TLS session. Target: TLS session
10. Investigation Playbook
- Trigger: Detection of GoAhead 6.1.0 or earlier, successful authentication with a revoked certificate, acceptance of unexpected certificate chains, or confirmation of DHE_RSA usage.
- Initial Checks: Check SBOMs, firmware, GoAhead versions, linked TLS backends, compile flags, and runtime configurations.
- Endpoint Investigation: Check target device audit logs, process or firmware integrity, and the presence of suspicious administrative operations.
- Identity and Cloud Investigation: Check client certificate serial numbers, CRL update status, established authentication sessions, and administrative account activity history.
- Follow-On Investigation: Investigate unauthorized configuration changes, creation of new credentials, and access to sensitive data.
- Containment: Isolate management interfaces, update firmware, rotate certificates and credentials, and revoke existing sessions.
- Classification: Clearly separate and record "vulnerable configuration match", "connection attempt", "successful authentication bypass", "decryption of communication data", and "subsequent administrative operations".
11. Defense and Detection Ideas
- Single Event: Detect successful authentication using a revoked client certificate's serial number or the acceptance of certificate chains exceeding policy depth.
- Time-Series Correlation: Correlate TLS handshake events, management session establishment, and configuration change events using client certificate serial numbers.
- Hunting: Inventory assets across the board for the combination of TLS 1.2 DHE_RSA usage and older GoAhead / Mbed TLS backends.
- Logging Gaps: Embedded devices may not log the type of TLS backend used or detailed client certificate properties (serial number, chain depth).
- Priority Controls: Prioritize applying GoAhead 6.1.1 or vendor-patched firmware, isolating management networks, layering mTLS with secondary authentication, and, for the DHE issue, disabling finite-field DHE cipher suites or migrating to TLS 1.3.
12. Facts / Inference / Hypothesis
Facts
- CVE-2026-115881 is an issue where OpenSSL-compatible backends using mTLS and CRLs fail to enforce the revocation verification flag even when a CRL is loaded, accepting revoked client certificates. It affects GoAhead 3.4.5 through 6.1.0 and has a CVSS score of 9.1.
- CVE-2026-115884 is an issue where LibreSSL 3.2.x or 3.3.2 through 3.3.6 under the configuration VERIFY_PEER=1 and VERIFY_ISSUER=0 accept certificate chains exceeding the allowed depth. It affects GoAhead through 6.1.0 and has a CVSS score of 7.4.
- In GoAhead 4.0.2 through 6.1.0 with the Mbed TLS backend, a length specification error treats a 2048-bit DH modulus as 1 byte, potentially allowing TLS 1.2 DHE_RSA sessions to be decrypted if the client accepts it. The referenced GitHub Security Advisory (GHSA-fmvx-2xfx-2gq4) does not list a CVE number.
- All three issues were resolved in GoAhead 6.1.1. Actual product impact depends on the adopted version, TLS backend, and compile/runtime configurations.
- No in-the-wild exploitation had been reported at the time of publication.
Inference
- Inference: Because impact cannot be determined solely from product names or GoAhead server banners, verification combining SBOMs, firmware build configurations, linked TLS libraries, and client authentication settings is required.
Hypothesis
- No additional hypotheses. Unverified items are noted in "Unknowns and Limitations".
13. MITRE ATT&CK Mapping
The source material does not provide sufficient evidence for a reliable ATT&CK mapping, so none is assigned.
14. Unknowns and Limitations
- The timeline and target versions for individual embedded product vendors to incorporate GoAhead 6.1.1 patches into their respective firmware must be verified on a product-by-product basis.
- Regarding the DHE weakening issue in the Mbed TLS backend, no CVE number is listed on the referenced GHSA. Organizations must also verify the Mbed TLS versions and cipher suite configurations adopted by each product.
15. Impact on SOCs and Organizations
When GoAhead is used in management interfaces of routers, network cameras, gateways, and industrial or embedded devices, organizations should check vendor advisories and firmware update information, and ensure that configurations do not rely on mTLS as the sole defense mechanism for management interfaces.
16. Summary by Role
- SOC: Investigate the acceptance of revoked certificates, abnormal certificate chains, and observations of TLS 1.2 DHE_RSA by separating them from evidence of successful authentication bypass or successful decryption.
- Administrators: Identify the GoAhead version, TLS backend, and settings within devices, and update to GoAhead 6.1.1 or vendor-provided patched versions.
- Users: Follow firmware update guidance from device vendors and ensure that device management screens are not exposed directly to the internet.
1 reaction
Mentions
GoAhead 3.4.5-6.1.0 (CVE-2026-115881): with OpenSSL+mTLS, trusted CA/issuer checks and a configured CRL, revoked trusted client certs can pass, EmbedThis reports. Fixed: 6.1.1. Not independently tested. github.com/embedthis/goahead/security/advisories/… docs.openssl.org
GoAhead TLS Flaws: Revoked Certificate Acceptance, Chain-Depth Bypass, and Weak DHE 1. Basic Information - Title: Choose your backend: three TLS bugs in GoAhead - Source: FoxIO - Date: 2026-10-26 - Original: FoxIO - Related Sources: SecurityWeek: TLS Flaws Found in GoAhead Web Server, GHSA-5m75-xq69-c3c5, GHSA-r392-vqwx-3r4g, GHSA-fmvx-2xfx-2gq4, GoAhead v6.1.1 - Related Malware: None specified - Related Threat Actors: None specified - Related CVEs: CVE-2026-115881, CVE-2026-115884 - Related Products: GoAhead 3.4.5 through 6.1.0, OpenSSL, LibreSSL, Mbed TLS - Severity: High 2. Executive Summary FoxIO has reported three TLS implementation flaws in the embedded web server GoAhead, affecting different TLS backends: OpenSSL, LibreSSL, and Mbed TLS. These include the failure to enforce Certificate Revocation Lists (CRLs) (CVE-2026-115881), the bypass of certificate chain depth verification (CVE-2026-115884), and a DHE weakening issue where a 2048-bit DH modulus is treated as 1 byte. All of these issues have been addressed in GoAhead 6.1.1. Because the TLS client authentication and communication confidentiality of web servers widely used in embedded devices can be disabled depending on the build-time TLS backend and configuration, organizations should check the impact on individual product firmware. 3. Attack Flow Below are three independent paths with different TLS backends and configuration conditions, rather than a sequential three-step attack. | Target Backend / Identifier | Attacker Action / Technique | Protocol / Presented Data Used | Defensive Indicators (Conditions / Artifacts) | | --- | --- | --- | --- | | OpenSSL-compatible backend (CVE-2026-115881) | Attempt mTLS connection using a revoked client certificate | TLS handshake (revoked client certificate) | In GoAhead 3.4.5 to 6.1.0, when mTLS and CRL are used, CRL checks are not enforced even if a CRL is loaded, allowing authentication to succeed | | LibreSSL backend (CVE-2026-115884) | Create and present a certificate chain containing intermediate CAs that exceed the allowed depth | TLS handshake (certificate chain exceeding allowed depth) | Occurs in GoAhead through 6.1.0 with LibreSSL 3.2.x or 3.3.2 through 3.3.6, under the VERIFY_PEER=1 and VERIFY_ISSUER=0 configuration, where the chain is accepted | | Mbed TLS backend (GHSA-fmvx-2xfx-2gq4) | Observe or interfere with TLS 1.2 DHE_RSA handshakes, exploit the 1-byte DH modulus to recover the shared secret and decrypt traffic | Passive observation or man-in-the-middle interference of TLS 1.2 DHE_RSA traffic | Occurs in GoAhead 4.0.2 to 6.1.0 with the Mbed TLS backend when the client accepts overly short DH parameters | mTLS Revocation Bypass 1. The attacker possesses a revoked client certificate and its corresponding private key. 2. The attacker establishes an mTLS connection to a GoAhead server using an OpenSSL-compatible backend configured with a CRL. 3. Due to CVE-2026-115881, even though the CRL file is loaded, the revocation verification flag is not enforced, allowing authentication with the revoked certificate to succeed. LibreSSL Chain Depth Bypass 1. The attacker creates a certificate chain that exceeds the configured allowed depth. 2. The attacker presents the chain to GoAhead running on a specific LibreSSL version and verification configuration (VERIFY_PEER=1 and VERIFY_ISSUER=0). 3. Due to CVE-2026-115884, the certificate chain violating the depth limit is accepted as is. Mbed TLS DHE Weakening 1. The attacker observes or interferes with TLS 1.2 DHE_RSA handshakes on the network. 2. Due to a length specification error on the GoAhead side, a 1-byte DH modulus is utilized, making it easier to calculate the shared secret. 3. If the connecting client accepts sessions containing such extremely short DH parameters, communication traffic may be decrypted. 4. Attacker Positioning and Execution Location - Positioned externally or internally with network access to the management interface of the target device, or located along the network path where TLS communication can be observed or interfered with. 5. Victim and Administrator Perspectives Victims - Connections appear completely normal, and explicit warnings may not appear in the browser or client. Administrators - May observe successful mTLS authentication using a revoked client certificate, the acceptance of certificate chains with unexpected depths, or negotiation of the TLS 1.2 DHE_RSA cipher suite. 6. Success and Failure Conditions Success Conditions - The target must be running an affected GoAhead version combined with a vulnerable TLS backend and configuration. - For DHE weakening, the conditions are met when negotiating TLS 1.2 DHE_RSA and the client accepts overly short DH parameters. ECDHE, TLS 1.3, and Mbed TLS 4.x with DHE cipher suites removed are not subject to this path. Failure Conditions and Mitigations - Update to GoAhead 6.1.1 or the patched firmware provided by the product vendor. - Isolate management interfaces at the network level, avoiding reliance solely on mTLS by combining multi-layer authentication and network allowlists. - For DHE weakening, mitigations include disabling finite field DHE cipher suites, migrating to TLS 1.3, or switching to an unaffected backend. However, migrating to TLS 1.3 alone does not fix GoAhead's CRL-enforcement flaw in OpenSSL-compatible builds or its chain-depth verification flaw with the affected LibreSSL verifier. 7. What Happens Upon Success - Client authentication bypass using revoked certificates, circumvention of certificate chain policies, or reduction in the confidentiality of TLS 1.2 sessions occurs. - However, actual impact depends on each product's build configuration and runtime settings, so the mere use of GoAhead does not automatically confirm vulnerability. 8. Observable Logs Inference: The following are potential logs to check within your organization. Their availability depends on log collection, retention, and product support, and they are distinct from observation records from threat intelligence sources. - Email: None available - Proxy / SWG / DNS: Check the client certificate subject, serial number, revocation status, and certificate chain depth in TLS handshakes. - Endpoint / EDR: None available - Identity / IdP: Check the history of administrative logins and configuration operations that occurred after successful mTLS authentication. - SaaS / Cloud: Check audit logs of the device management interface and version information of firmware components. - Network: Check for TLS 1.2 DHE_RSA negotiation or the presentation of unusual certificate chains. 9. Attack Success Assessment - Attack Attempt Observed (Success Unconfirmed) (contact_only): Criteria: TLS handshake attempts or detection of vulnerable versions do not indicate successful authentication bypass or traffic decryption. Target: Device management surface - Malware Execution or Authentication Success Confirmed (malware_or_authentication_success): Criteria: Confirm evidence that an authentication session was established using a revoked certificate or a policy-violating certificate chain. Target: mTLS session - Data Theft or Session Compromise Confirmed (data_or_session_compromise): Criteria: For the Mbed TLS backend case, independently corroborate actually decrypted application data with the corresponding TLS session. Target: TLS session 10. Investigation Playbook - Trigger: Detection of GoAhead 6.1.0 or earlier, successful authentication with a revoked certificate, acceptance of unexpected certificate chains, or confirmation of DHE_RSA usage. - Initial Checks: Check SBOMs, firmware, GoAhead versions, linked TLS backends, compile flags, and runtime configurations. - Endpoint Investigation: Check target device audit logs, process or firmware integrity, and the presence of suspicious administrative operations. - Identity and Cloud Investigation: Check client certificate serial numbers, CRL update status, established authentication sessions, and administrative account activity history. - Follow-On Investigation: Investigate unauthorized configuration changes, creation of new credentials, and access to sensitive data. - Containment: Isolate management interfaces, update firmware, rotate certificates and credentials, and revoke existing sessions. - Classification: Clearly separate and record "vulnerable configuration match", "connection attempt", "successful authentication bypass", "decryption of communication data", and "subsequent administrative operations". 11. Defense and Detection Ideas - Single Event: Detect successful authentication using a revoked client certificate's serial number or the acceptance of certificate chains exceeding policy depth. - Time-Series Correlation: Correlate TLS handshake events, management session establishment, and configuration change events using client certificate serial numbers. - Hunting: Inventory assets across the board for the combination of TLS 1.2 DHE_RSA usage and older GoAhead / Mbed TLS backends. - Logging Gaps: Embedded devices may not log the type of TLS backend used or detailed client certificate properties (serial number, chain depth). - Priority Controls: Prioritize applying GoAhead 6.1.1 or vendor-patched firmware, isolating management networks, layering mTLS with secondary authentication, and, for the DHE issue, disabling finite-field DHE cipher suites or migrating to TLS 1.3. 12. Facts / Inference / Hypothesis Facts - CVE-2026-115881 is an issue where OpenSSL-compatible backends using mTLS and CRLs fail to enforce the revocation verification flag even when a CRL is loaded, accepting revoked client certificates. It affects GoAhead 3.4.5 through 6.1.0 and has a CVSS score of 9.1. - CVE-2026-115884 is an issue where LibreSSL 3.2.x or 3.3.2 through 3.3.6 under the configuration VERIFY_PEER=1 and VERIFY_ISSUER=0 accept certificate chains exceeding the allowed depth. It affects GoAhead through 6.1.0 and has a CVSS score of 7.4. - In GoAhead 4.0.2 through 6.1.0 with the Mbed TLS backend, a length specification error treats a 2048-bit DH modulus as 1 byte, potentially allowing TLS 1.2 DHE_RSA sessions to be decrypted if the client accepts it. The referenced GitHub Security Advisory (GHSA-fmvx-2xfx-2gq4) does not list a CVE number. - All three issues were resolved in GoAhead 6.1.1. Actual product impact depends on the adopted version, TLS backend, and compile/runtime configurations. - No in-the-wild exploitation had been reported at the time of publication. Inference - Inference: Because impact cannot be determined solely from product names or GoAhead server banners, verification combining SBOMs, firmware build configurations, linked TLS libraries, and client authentication settings is required. Hypothesis - No additional hypotheses. Unverified items are noted in "Unknowns and Limitations". 13. MITRE ATT&CK Mapping The source material does not provide sufficient evidence for a reliable ATT&CK mapping, so none is assigned. 14. Unknowns and Limitations - The timeline and target versions for individual embedded product vendors to incorporate GoAhead 6.1.1 patches into their respective firmware must be verified on a product-by-product basis. - Regarding the DHE weakening issue in the Mbed TLS backend, no CVE number is listed on the referenced GHSA. Organizations must also verify the Mbed TLS versions and cipher suite configurations adopted by each product. 15. Impact on SOCs and Organizations When GoAhead is used in management interfaces of routers, network cameras, gateways, and industrial or embedded devices, organizations should check vendor advisories and firmware update information, and ensure that configurations do not rely on mTLS as the sole defense mechanism for management interfaces. 16. Summary by Role - SOC: Investigate the acceptance of revoked certificates, abnormal certificate chains, and observations of TLS 1.2 DHE_RSA by separating them from evidence of successful authentication bypass or successful decryption. - Administrators: Identify the GoAhead version, TLS backend, and settings within devices, and update to GoAhead 6.1.1 or vendor-provided patched versions. - Users: Follow firmware update guidance from device vendors and ensure that device management screens are not exposed directly to the internet.
🔐 GoAhead : CVE-2026-115881 permet à des certificats révoqués d'être acceptés sur certaines configurations mTLS/OpenSSL. Aucune exploitation connue. Vérifiez vos firmwares : corrigé en 6.1.1. #Cyber github.com/embedthis/goahead/security/advisories/…
Critical GoAhead flaw allows revoked certificates to bypass authentication A critical vulnerability in the GoAhead embedded web server causes revoked client certificates to remain valid on certain mutual TLS deployments. Tracked as CVE-2026-115881, the flaw carries a CVSS score of 9.1 and affects GoAhead versions 3.4.5 through 6.1.0. ⠀ GoAhead loads the configured certificate revocation list but fails to enable the OpenSSL flag that actually enforces it. An attacker possessing a previously trusted certificate and its private key could continue accessing protected services after the certificate was revoked. ⠀ Researchers also disclosed two related TLS flaws: • CVE-2026-115884: Certain LibreSSL builds may accept an overlong certificate chain, CVSS 7.4 • GOAHEAD-SA-2026-0005: Mbed TLS builds may use a one-byte Diffie-Hellman modulus, allowing some recorded TLS 1.2 sessions to be decrypted, CVSS 5.9 ⠀ GoAhead is embedded in management interfaces for routers, printers, gateways and industrial equipment. Exposure depends on the TLS library and configuration used by each device, so the widespread use of GoAhead does not mean every device is vulnerable. ⠀ All three flaws were fixed in GoAhead 6.1.1. Device owners may need to wait for firmware containing the update from their equipment manufacturer. Source: github.com/embedthis/goahead/security/advisories/…
🚨🇺🇸 Critical GoAhead flaw allows revoked certificates to bypass authentication A critical vulnerability in the GoAhead embedded web server causes revoked client certificates to remain valid on certain mutual TLS deployments. Tracked as CVE-2026-115881, the flaw carries a CVSS score of 9.1 and affects GoAhead versions 3.4.5 through 6.1.0. ⠀ GoAhead loads the configured certificate revocation list but fails to enable the OpenSSL flag that actually enforces it. An attacker possessing a previously trusted certificate and its private key could continue accessing protected services after the certificate was revoked. ⠀ Researchers also disclosed two related TLS flaws: • CVE-2026-115884: Certain LibreSSL builds may accept an overlong certificate chain, CVSS 7.4 • GOAHEAD-SA-2026-0005: Mbed TLS builds may use a one-byte Diffie-Hellman modulus, allowing some recorded TLS 1.2 sessions to be decrypted, CVSS 5.9 ⠀ GoAhead is embedded in management interfaces for routers, printers, gateways and industrial equipment. Exposure depends on the TLS library and configuration used by each device, so the widespread use of GoAhead does not mean every device is vulnerable. ⠀ All three flaws were fixed in GoAhead 6.1.1. Device owners may need to wait for firmware containing the update from their equipment manufacturer. Source: github.com/embedthis/goahead/security/advisories/…
Sources: FoxIO writeup foxio.io and EmbedThis advisory github.com/embedthis/goahead/security/advisories/…
GoAhead serverio spragos leidžia prisijungti su atšauktu sertifikatu GoAhead yra mažas žiniatinklio serveris. Jį naudoja maršrutizatoriai, spausdintuvai ir pramoniniai valdikliai. Gamintojas EmbedThis paskelbė tris TLS spragas. Pavojingiausia yra CVE-2026-115881 (CVSS 9.1). Serveris įkelia atšauktų sertifikatų sąrašą, bet jo netaiko. Todėl pavogtas ar atšauktas sertifikatas vis tiek veikia. Kita klaida Mbed TLS versijose leidžia iššifruoti dalį TLS 1.2 sesijų. Išnaudojimo atvejų kol kas nepranešta. Praktinė rekomendacija. Klauskite įrenginių gamintojų apie atnaujinimus su GoAhead 6.1.1. Kritinei spragai laikino sprendimo nėra, todėl atnaujinimai būtini. Šaltinis (EmbedThis saugumo pranešimas ir FoxIO tyrimas) github.com/embedthis/goahead/security/advisories/… foxio.io
respectfully, iot was a mistake
ルーター・プリンター・産業機器などの管理画面に組み込まれる小型Webサーバー「GoAhead」に複数の脆弱性。最も重いのはOpenSSL版で、失効リスト（CRL）を読み込むのに確認が有効化されず、盗難・廃棄で失効させたクライアント証明書でもmTLS接続が通ってしまう問題（開発元評価9.1、mTLSとCRLを自分で設定した構成のみ。Mbed TLS版は対象外）。修正は6.1.1。利用者は各メーカーのファーム更新を確認。 github.com/embedthis/goahead/security/advisories/…
@IntCyberDigest Full story: pickax.com Sources: foxio.io github.com/embedthis/goahead/releases/tag/v6.1.1