CVE-2026-96770 s2s-proxy accepts untrusted client certificates
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: total
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| temporalio github.com/temporalio/s2s-proxy(Go) | >= 0.0.1-alpha, <= 0.2.2 | after 0.2.2 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| temporalio github.com/temporalio/s2s-proxy(Go) | >= 0.0.1-alpha, <= 0.2.2 | No fix listed |
References
- Affected TLS server configuration in s2s-proxy 0.2.2 product
- Change that introduced the affected certificate verification mode product
- Fix pull request patch
- Fix commit patch
- Temporal Payload Codec and Codec Server documentation product
- ENISA EUVD EUVD-2026-85567 third-party-advisory