EM-20261110-8SED
VulnerabilityInfo severity
Rack Vulnerability (CVE-2026-125108)
CVE-2026-125108
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 09 21:55 UTCC41 Red Hat Security Data
- Page Born
- Nov 10 19:26 UTCsecond source joined
- Last Signal
- Nov 10 19:26 UTC7 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 27 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 09 22:18 UTCC6 NVD published
- Scored: reachedNov 09 22:18 UTCCVSS 3.7 · EPSS 0.2%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 09 21:55 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-p8x9-v4hv-2w4g / CVE-2026-125108: Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass (opens source in a new tab) rubygems:rack, rubygems:rack, rubygems:rack Info severityDatabaseC26 GitHub Advisory Database
- Red Hat: CVE-2026-125108 (low) (opens source in a new tab) rack: rack: Security inspection bypass via multipart boundary parsing differential Info severityVendorC41 Red Hat Security Data