{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-96770 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-96770 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-96770 is a critical authentication bypass vulnerability in Temporal Technologies, Inc. s2s-proxy, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-96770 and fix it if it is affected.\n\nWhat it is: CVE-2026-96770 is a critical authentication bypass vulnerability in Temporal Technologies, Inc. s2s-proxy, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-96770 in the wild and no public exploit code.\n\nAffected product: Temporal Technologies, Inc. s2s-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-96770/ (Markdown: https://insights.sbomify.com/CVE-2026-96770/index.md)","id":"CVE-2026-96770","markdown":"https://insights.sbomify.com/CVE-2026-96770/index.md","name":"CVE-2026-96770","record":{"aliases":["GHSA-fhc4-rg5x-86fx"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Temporal s2s-proxy","requires_auth":"none","summary":"Attackers can bypass TLS client certificate verification to establish connections and invoke RPCs without valid credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Temporal","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-296","name":"Improper Following of a Certificate's Chain of Trust"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"s2s-proxy accepts untrusted client certificates","id":"CVE-2026-96770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Intelliants Subrion CMS actions.json assign-owner information disclosure","id":"CVE-2026-96772"},"packages":[],"prev":{"headline":"GoSMTP Pro \u003c= 1.2.3 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Email Log Body","id":"CVE-2026-96768"},"products":["s2s-proxy"],"published":"2026-09-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Temporal Technologies, Inc."]},"summary":"Attackers can bypass TLS client certificate verification to establish connections and invoke RPCs without valid credentials.","url":"https://insights.sbomify.com/CVE-2026-96770/"}