rewindex

RewindexCVEsTemporal Cloud

CVE-2026-96770: s2s-proxy accepts untrusted client certificates

Critical · CVSS 9.3 (CVSS 4.0)EPSS 0.32%, 25th percentilePublished Updated Assigner: Temporal

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.

CWE-296

Tracked companies

Temporal Cloud

Mapped from the CVE’s affected-product data, NVD CPE matches, vendor advisories or package feeds. A mapping means the vendor’s software is named, not that its hosted service was exposed.

Status incidents that name it

No tracked status incident names this CVE.

Affected vendors and products

Temporal Technologies, Inc.: s2s-proxy

References

All CVEsMarkdownJSON