CVE-2026-111943: 
Go Schwachstellenanalyse und -minderung

CVE-2026-111943 is an improper certificate validation vulnerability in the Go standard library's crypto/x509 package that enables man-in-the-middle (MitM) attacks via compromised intermediate certificates from the eMudhra Certificate Authority. The vulnerability arises because on certain platforms, system trust stores may not be automatically updated to distrust the compromised eMudhra (emsign) intermediate CA certificates, leaving applications built with affected Go versions susceptible to TLS interception. Affected versions are Go crypto/x509 before 1.26.10 and 1.27.0-0 through 1.27.3. The vulnerability was disclosed on October 20, 2026, with Go releasing emergency patches (1.26.10 and 1.27.3) the same day. It carries a CVSS v3.1 base score of 6.8 (Medium) (Red Hat CVE, Openwall oss-sec).

The root cause is classified as CWE-295 (Improper Certificate Validation). Eight intermediate CA private keys belonging to eMudhra's emsign CA hierarchy were found to be recoverable due to flawed key generation (weak P-384 entropy), meaning an attacker who recovers these keys can forge TLS certificates for any domain chained through those intermediates. While most platforms rely on system trust stores (which major browsers and OSes updated promptly), Go applications on platforms where trust store updates are not automatic remained vulnerable. The Go team's mitigation added a hardcoded denylist in crypto/x509 so that Verify() returns an error when any of the eight known compromised intermediate certificates appear in a chain, regardless of system trust store state. The fix is tracked in Go issue #82345 and change list CL 851047 (Openwall oss-sec, Red Hat Bugzilla).

Successful exploitation allows an unauthenticated network attacker to perform MitM attacks against TLS-encrypted communications in Go applications that trust the compromised eMudhra intermediate certificates. An attacker who has recovered one of the eight weak intermediate CA private keys can forge valid-appearing TLS certificates for arbitrary domains, enabling interception and decryption of HTTPS traffic, credential theft, and injection of malicious content. The confidentiality and integrity of all data transmitted over affected TLS connections is at risk; availability is not directly impacted. The scope is limited to Go applications on platforms where system trust stores were not updated, but the breadth of Go's use in cloud-native and infrastructure tooling (Docker, Terraform, Kubernetes tooling, etc.) makes the potential blast radius significant (Red Hat CVE, Feedly).

No confirmed in-the-wild exploitation has been reported as of the disclosure date. A GitHub repository (phpc0de/CVE-2026-111943-Remediator) exists but has been assessed as a detection and remediation scanner, not exploit code. The EPSS score is 0.00145 (approximately 0.15%), indicating low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, the underlying eMudhra key compromise is a real-world CA incident that prompted emergency responses from Mozilla, Google, Apple, and Microsoft to block the affected certificates in their trust stores (Red Hat CVE, Feedly).

1. Recover compromised CA private key: Obtain one of the eight eMudhra intermediate CA private keys, which were recoverable due to weak P-384 entropy in key generation (the keys were effectively small integers, e.g., the scalar value "4").
2. Forge a TLS certificate: Use the recovered intermediate CA private key to sign a fraudulent TLS certificate for a target domain (e.g., a banking or enterprise application), creating a certificate that chains to the compromised eMudhra intermediate.
3. Position for MitM: Gain a network position between the victim Go application and the target server (e.g., via ARP spoofing, DNS poisoning, BGP hijacking, or a rogue Wi-Fi access point).
4. Present forged certificate: Intercept the TLS handshake and present the forged certificate to the victim Go application. On unpatched Go versions (< 1.26.10 or 1.27.0–1.27.2), crypto/x509.Verify() will accept the chain if the system trust store has not been updated to distrust the eMudhra intermediates.
5. Decrypt and manipulate traffic: With the MitM position established, decrypt, read, or modify the encrypted communications between the victim application and the legitimate server (Openwall oss-sec, Red Hat Bugzilla).

• Network: Unexpected TLS certificates presented to Go applications that chain through eMudhra/emsign intermediate CAs (check certificate Subject/Issuer fields for eMudhra or emsign); anomalous TLS handshake failures or certificate errors in application logs after patching.
• Logs: Go application errors referencing crypto/x509 certificate verification failures mentioning blocked intermediate certificates after upgrading to Go 1.26.10 or 1.27.3; TLS connection errors to services that previously succeeded.
• File System: Presence of unpatched Go binaries (version < 1.26.10 or 1.27.0–1.27.2) identified via go version or binary inspection; outdated system CA certificate bundles that still include eMudhra intermediate certificates.
• Process/Runtime: Go applications making outbound TLS connections that do not fail when presented with eMudhra-chained certificates on unpatched systems (detectable via Qualys or Nessus scanner plugins referencing this CVE).

The primary remediation is to upgrade Go to version 1.26.10 or 1.27.3 (or later), which include a hardcoded denylist in crypto/x509 blocking the eight compromised eMudhra intermediate certificates. Additionally, ensure system root certificate trust stores are updated on all platforms — Mozilla, Google, Apple, and Microsoft have all pushed emergency revocations of the affected eMudhra certificates. Red Hat has issued numerous errata (RHSA-2026:86093 through RHSA-2026:91138) covering RHEL 8, 9, 10, OpenShift, and OpenStack. SUSE, AlmaLinux, Amazon Linux, Debian, and other distributions have also released updates. Organizations should audit all Go-based applications and container images for the affected versions and rebuild/redeploy with patched Go toolchains (Openwall oss-sec, Red Hat Bugzilla).

The eMudhra CA key compromise generated significant industry attention, with Mozilla, Google, Apple, and Microsoft all issuing emergency trust store updates to block the eight compromised intermediate certificates. Forrester published a blog post calling the incident "a wake-up call for enterprise PKI." Cisco Talos published analysis on the compromised intermediate certificates. Qualys released operational detection tools and a blog post explaining how to identify affected systems using CVE-2026-111943 scanner plugins. The story trended on Hacker News (multiple threads), Mastodon, and Bluesky, with community discussion focusing on the remarkable weakness of the eMudhra key generation (one key's private scalar was reportedly the integer 4). Multiple security blogs (BleepingComputer, The Hacker News, SecurityOnline, Checkmarx, Endor Labs, SOCRadar) covered the incident extensively, and the Go team's emergency release was widely praised for the rapid denylist approach (Feedly).