EM-20261109-426N
VulnerabilityMedium severity
OmniAuth Vulnerability (CVE-2026-63183)
CVE-2026-63183
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 04 19:07 UTCC41 Red Hat Security Data
- Page Born
- Nov 09 21:49 UTCsecond source joined
- Last Signal
- Nov 09 21:49 UTC4 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 5 daysso 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 04 19:17 UTCC6 NVD published
- Scored: reachedNov 04 19:17 UTCCVSS 6.9 · EPSS 0.2%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 04 19:07 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
- GHSA-m27g-v28p-f9fx / CVE-2026-63183: OmniAuth: Host Header Injection Vulnerability (opens source in a new tab) rubygems:omniauth Med severityDatabaseC26 GitHub Advisory Database
- Red Hat: CVE-2026-63183 (moderate) (opens source in a new tab) omniauth: OmniAuth: Host header injection via forged HTTP Host header Med severityVendorC41 Red Hat Security Data