Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-120967 — Python PoC and Docker lab demonstrating CVE-2026-120967, an nginx stream SNI client certificate verification bypass that lets clients reach mTLS-protected backends without a certificate. | Kitploit
Tools/GitHubGitHub/llcforge/cve-2026-120967
Vulnerability AnalysisExploitationWeb SecurityNetwork SecurityAuthenticationLabs & Practice
GitHubllcforge/cve-2026-120967

CVE-2026-120967

Python PoC and Docker lab demonstrating CVE-2026-120967, an nginx stream SNI client certificate verification bypass that lets clients reach mTLS-protected backends without a certificate.

View Repository
3 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    647
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    421
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    389
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    333
  • 6

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    331

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-120967

nginx — Stream SNI Client Certificate Verification Bypass

CVSS CWE Language Fixed Disclosed


Overview

nginx's stream SSL module applies ssl_verify_client checks too late in the handshake pipeline when multiple virtual servers share the same listen socket and are differentiated by SNI. A client that sends the SNI hostname of a certificate-protected server block but omits the client certificate can bypass mutual TLS and reach the protected backend.

FieldValue
CVECVE-2026-120967
CVSS 3.14.8 Medium — AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CWECWE-295 (Improper Certificate Validation)
Componentngx_stream_ssl_module (SNI routing)
Affectednginx 1.25.5 – 1.31.8
Fixednginx 1.30.7 / 1.31.9
Auth RequiredNone
Disclosed2026-11-18

Vulnerability Details

When two stream servers share the same socket address and differ only by ssl_server_name, nginx selects the server block based on the TLS SNI extension. In affected versions the ssl_verify_client check associated with the selected server block is applied after the stream routing decision has already been committed. A client that sends SNI = secure.test but omits the client certificate is routed to the protected backend without triggering the certificate verification failure.

Lab layout:

nginx:1.31.8  stream  :9443
  server { ssl_server_name default.invalid; ... }          ← no mTLS
  server { ssl_server_name secure.test;                    ← mTLS required
           ssl_verify_client on;
           ssl_client_certificate ca.pem; ... }
         ↓
backend (raw TCP) — replies "secret" to any request

Attack Flow

flowchart LR
    A([Attacker\nNo client cert]) -->|TLS SNI = secure.test\nNo client certificate| B[nginx stream\n1.31.8]
    B -->|SNI matches protected\nserver block| C{ssl_verify_client\napplied AFTER routing}
    C -->|Routes to backend\nbefore cert check| D[Protected Backend\nAccessed]
    D --> E([mTLS Bypass\nConfidential data exposed])

    style A fill:#3d1a1a,stroke:#f85149,color:#f85149
    style E fill:#1a1f2e,stroke:#58a6ff,color:#58a6ff

PoC Usage

Warning: Docker Compose lab environment only.

Setup

docker compose up --build -d
sleep 5

Run the bypass

python3 poc.py

Expected output — vulnerable nginx:

[+] BYPASS CONFIRMED — backend reached without client certificate!
    SNI: secure.test  cert: none  response: "secret"
[!] VULNERABLE — ssl_verify_client bypassed via SNI routing race

Options

python3 poc.py --host 127.0.0.1 --port 9443
FlagDescription
--host HOSTnginx host (default: 127.0.0.1)
--port PORTStream port (default: 9443)
--sni NAMESNI hostname to send (default: secure.test)
--no-certSkip client certificate (default — this is the bypass)
--with-certProvide a valid client cert (baseline — should succeed)

Baseline — legitimate access with client certificate

python3 poc.py --with-cert
# Expected: HTTP 200, backend reached with valid cert

Expected output — patched build

# nginx 1.31.9
python3 poc.py
# TLS error: certificate verify failed
# [+] NOT vulnerable — ssl_verify_client enforced before routing

Detection

IndicatorNotes
TLS handshake succeeded on mTLS port without SSL_client_cert log fieldnginx access log: check for missing $ssl_client_cert
Backend reached from unexpected clientsBackend access log: connections without valid client identity
SNI secure.test in TLS handshake without client certNetwork capture: ClientHello with SNI but no Certificate handshake message

Impact

An attacker on a network that can reach the nginx stream port can bypass mutual TLS authentication and connect to any backend that relies solely on nginx's ssl_verify_client on for access control.


Remediation

Upgrade to nginx 1.30.7 or 1.31.9. The fix ensures ssl_verify_client is enforced before the routing decision is committed.

ActionDetail
Upgrade nginx1.30.7 (stable) or 1.31.9 (mainline)
WorkaroundMove mTLS servers to dedicated listen sockets (not shared with non-mTLS)
Backend validationAdd mutual TLS validation at the backend layer as defense-in-depth

References

  • nginx Security Advisories: https://nginx.org/en/security_advisories.html
  • CWE-295: https://cwe.mitre.org/data/definitions/295.html
  • CVE Record: https://www.cve.org/CVERecord?id=CVE-2026-120967

Disclaimer: For authorized security research and controlled lab use only. MIT License.

Download Tool