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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
23 Sep 2026, 19:19
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-23 19:19
Updated : 2026-09-24 20:43
NVD link : CVE-2026-96770
Mitre link : CVE-2026-96770
CVE.ORG link : CVE-2026-96770
JSON object : View
Products Affected
No product.
CWE
CWE-296
Improper Following of a Certificate's Chain of Trust
