[ CVE-2026-96770 · Published 23 Sep 2026 ]
Vulnerability in Temporal Technologies, Inc. s2s-proxy
[ Why it matters ]Priority signals
- Critical severity: CVSS 9.3
[ Description ]Official description
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.
[ Fixes ]Fixes and patches
No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.
[ References ]References
- docs.temporal.io/production-deployment/data-encryption
- github.com/temporalio/s2s-proxy/blob/v0.2.2/encryption/tls.go
- github.com/temporalio/s2s-proxy/commit/d100c2258dbc37d7df51298ea045315f36c7eb3b
- github.com/temporalio/s2s-proxy/commit/f1dc6b9a3919d37e82545ab461cbe6bb62618d3c
- github.com/temporalio/s2s-proxy/pull/296