CVE-2026-96770

published 23 Sep 2026 · updated 23 Sep 2026

s2s-proxy accepts untrusted client certificates

9.3CriticalCVSS 9.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Temporal Technologies>=0.0.1-alpha <=0.2.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-96770 severity on Zeptric[![CVE-2026-96770](https://zeptric.io/badge/cve/CVE-2026-96770.svg)](https://zeptric.io/cve/CVE-2026-96770)