EM-20261030-KZEC VulnerabilityHigh severity

crass Vulnerability (CVE-2026-61847)

CVE-2026-61847

Status

Developing

Since Oct 30 18:44 UTC: signals keep joining.

First Signal: Oct 29 16:35 UTCC26 GitHub Advisory Database
Page Born: Oct 30 18:44 UTCsecond source joined
Last Signal: Oct 30 18:44 UTC5 days before snapshot
Sources: 21 official · 1 research, news or crowd
Open For: 6 daysso far

Life Of This Page

1
Born

Oct 30 18:44 UTC
A second, independent source names it.
2
Developing · Now

Oct 30 18:44 UTC
New signals join; severity can move.
3
Confirmed

Not yet
CISA KEV lists it, or exploitation in the wild is reported.
4
Resolved

Not yet
Past the fix deadline and 14 days with no new signal.
5
Archived

Not yet
30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The address and ID never change. 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: reached

Oct 29 16:35 UTC
C26 first to name it
Scored: reached

Oct 29 16:35 UTC
No CVSS yet · EPSS 0.5%
Exploited: not yet

Not yet
No exploitation reported
Advisories: not yet

Not yet
None yet
Vendor Response: reached

Oct 30 18:44 UTC
C41 published
Resolved: not yet

Not yet
After 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

Oct 30 18:44 UTCRed Hat: CVE-2026-61847 (important) (opens source in a new tab) crass: crass: Denial of Service via excessive recursion when processing comments High severityVendorC41 Red Hat Security Data
Oct 29 16:35 UTCGHSA-wwpr-jff3-395c / CVE-2026-61847: Cra : A large number of adjacent CSS comment can trigger a Sy temStackError (opens source in a new tab) rubygems:crass Med severityDatabaseC26 GitHub Advisory Database