EM-20261118-H611
VulnerabilityHigh severity
Vulnerability (CVE-2026-120967)
CVE-2026-120967
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 18 15:23 UTCC41 Red Hat Security Data
- Page Born
- Nov 18 16:44 UTCsecond source joined
- Last Signal
- Nov 18 16:44 UTC38 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 12 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 18 16:18 UTCC6 NVD published
- Scored: reachedNov 18 16:18 UTCCVSS 6.3
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 18 15:23 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- Public exploit: Exploit for CVE-2026-120967 (opens source in a new tab) # CVE-2026-120967 — nginx stream SNI client-certificate verification bypass Proof-of-concept lab demonstrating a client-certificate verification bypass in nginx's stream module when multiple virtual servers share the… High severityResearch & NewsC31 Vulners (new public exploits)
- Red Hat: CVE-2026-120967 (moderate) (opens source in a new tab) Med severityVendorC41 Red Hat Security Data