Event Monitor Cyber
EM-20261112-9BR1 VulnerabilityMedium severity

Loofah Vulnerability (CVE-2026-126206)

CVE-2026-126206

Share
Status
Developing

Since : signals keep joining.

First Signal
Nov 12 20:51 UTCC41 Red Hat Security Data
Page Born
Nov 12 20:56 UTCsecond source joined
Last Signal
Nov 12 20:56 UTC19 hours before snapshot
Sources
21 official · 1 research, news or crowd
Open For
4 hoursso far

Life Of This Page

  1. 1
    Born
    A second, independent source names it.
  2. 2
    Developing · Now
    New signals join; severity can move.
  3. 3
    Confirmed
    Not yet
    CISA KEV lists it, or exploitation in the wild is reported.
  4. 4
    Resolved
    Not yet
    Past the fix deadline and 14 days with no new signal.
  5. 5
    Archived
    Not yet
    30 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

  1. Disclosed: reached
    Nov 12 21:17 UTC
    C6 NVD published
  2. Scored: reached
    Nov 12 21:17 UTC
    CVSS 5.3
  3. Exploited: not yet
    Not yet
    No exploitation reported
  4. Advisories: not yet
    Not yet
    None yet
  5. Vendor Response: reached
    Nov 12 20:51 UTC
    C41 published
  6. Resolved: not yet
    Not yet
    After 14 quiet days

Timeline

16:0018:0020:0022:00Nov 13BornC41 Red Hat Security DataC26 GitHub Advisory Database

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

  1. GHSA-jcff-cj73-4w4f / CVE-2026-126206: Loofah allowed_uri? treats data:text/html as safe text/plain (opens source in a new tab) rubygems:loofah Med severityDatabaseC26 GitHub Advisory Database
  2. Red Hat: CVE-2026-126206 (moderate) (opens source in a new tab) loofah: Loofah: Cross-site scripting via improper data URI validation Med severityVendorC41 Red Hat Security Data