Monitoring

Critical vulnerability — CVE-2026-54906

Cyber·● resolved·Tier 2 · observational·149d active
Level9.8/ 10

Signals

  • CVSS9.8
  • SeverityCRITICAL
  • Other 9.0+12

Cite this situation

Monitoring Room, "Critical vulnerability — CVE-2026-54906", situation page, level 9.8/10 (Monitoring Room's 0–10 severity score), as of 2026-06-24 17:17 UTC, source: NIST NVD. https://monitoringroom.com/s/cyber-CVE-2026-54906

Call what happens next

Outages

Will GitHub report a major or critical incident between 16–22 November 2026?

No calls yetas of 14:53 UTC
Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-16 00:00 → 2026-11-23 00:00 UTC (end not included); calls close 2026-11-22 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-16T00:00:00.000Z up to (not including) 2026-11-23T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

Calls close 22 Nov, 00:00 UTC · Resolves from githubstatus.com

Related situations

Browse all situations →
Source · NIST NVD
Open primary →