Comparison Overview
UC Davis Undergraduate Education

UC Davis Undergraduate Education
The Grove (formerly Surge III), Davis, 95616, US
Last Update: 07/02/2026
Our office provides campuswide leadership for the delivery of undergraduate education and the enhancement of educational effectiveness and academic success. We act as liaison on academic issues pertinent to undergraduate education with each of the colleges and other cam...

University of North Texas
1155 Union Circle #311277, Denton, Tx, US, 76203-1277
Last Update: 02/04/2026
Ranked a Tier One research university by the Carnegie Classification, UNT is the flagship of the UNT System and is located in Denton, Texas. With 242 degree programs and a thriving community of nearly 44,000 students, UNT serves the North Texas region and helps drive th...
Compliance Ranges Comparison

UC Davis Undergraduate Education







University of North Texas






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for UC Davis Undergraduate Education in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of North Texas in 2026.
Incident History - UC Davis Undergraduate Education (X = Date, Y = Severity)
UC Davis Undergraduate Education cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of North Texas (X = Date, Y = Severity)
University of North Texas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UC Davis Undergraduate Education

University of North Texas
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.