CVE-2026-967709.3CriticalCWE-296

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

Temporal Technologies, Inc. · s2s-proxy

Vendor fix available · Affected: Temporal Technologies, Inc. s2s-proxy · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days

25th percentile

050100

Higher than 25% of scored CVEs

9.3CriticalCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Temporal Technologies, Inc. · s2s-proxyfrom 0.0.1-alpha up to and including 0.2.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Following of a Certificate's Chain of Trust · Cryptography
Vendor: Temporal Technologies, Inc.
Published: September 2026
Band: Unlikely (under 1%), September 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-96770 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.