CVE-2026-96770
All published s2s-proxy versions through 0.2.2 are affected. In …
All published s2s-proxy versions through 0.2.2 are affected. In versions 0.1.16 through 0.2.2, TLS server listeners use Go's RequireAnyClientCert mode when skipCAVerification is false. This mode checks that the client holds the certificate's private key but does not verify the certificate against the configured CA. An attacker can therefore use a self-signed certificate and key to establish a TLS and yamux connection, then invoke RPCs allowed by the proxy's configuration and Temporal credentials. No certificate or private key trusted by the deployment, and no Temporal credential, is required.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.temporal.io/production-deployment/data-encryption#codec-server-setup
- github.com/temporalio/s2s-proxy/blob/v0.2.2/encryption/tls.go#L47-L62
- github.com/temporalio/s2s-proxy/commit/d100c2258dbc37d7df51298ea045315f36c7eb3b
- github.com/temporalio/s2s-proxy/commit/f1dc6b9a3919d37e82545ab461cbe6bb62618d3c
- github.com/temporalio/s2s-proxy/pull/296
- nvd.nist.gov/vuln/detail/CVE-2026-96770
- cve.org/CVERecord?id=CVE-2026-96770
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.