PoC Monitor
← All CVEs
CVE-2026-96770published 23 Sep 2026 18:58 UTCData: JSON · API

Temporal Technologies, Inc. s2s-proxy

s2s-proxy accepts untrusted client certificates

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.3critical · scored by CNA · CWE-296
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Temporal Technologies, Inc. s2s-proxy
  • >= 0.0.1-alpha, <= 0.2.2

Mitigation

The fix is expected in version 0.2.3. Upgrade to version 0.2.3 or later when available.

Workaround

Restrict the listener to known peer addresses or a private network, or use a TLS terminator that verifies client certificates against the intended CA. These controls reduce exposure but do not fix the proxy defect.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published23 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
PoC Indexhttps://docs.temporal.io/production-deployment/data-encryption#codec-server-setupunknown14 Nov 2026