Vulnerability in Temporal Technologies, Inc. S2s-Proxy
CVE-2026-96770
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.
Published · last modified .
EPSS exploit prediction
EPSS: 0.003 (25.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 25th percentile — 25.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: +0.001
Affected products
Weakness classification (CWE)
References
- github.com/temporalio/s2s-proxy/blob/v0.2.2/encryption/tls.go (product)
- github.com/temporalio/s2s-proxy/commit/d100c2258dbc37d7df51298ea045315f36c7eb3b (product)
- github.com/temporalio/s2s-proxy/pull/296 (patch)
- github.com/temporalio/s2s-proxy/commit/f1dc6b9a3919d37e82545ab461cbe6bb62618d3c (patch)
- docs.temporal.io/production-deployment/data-encryption (product)