Comparison Overview
UC Santa Cruz Social Sciences

UC Santa Cruz Social Sciences
1156 High St, Santa Cruz, California, US, 95060
Last Update: 13/02/2026
As social, economic, political, and technological changes transform global society, social scientists are tackling extremely complex issues, from racism, economic inequity, educational reform, and governance to environmental degradation, international trade and finance,...

Texas A&M University
805 Rudder Tower, College Station, TX, US, 77843
Last Update: 19/06/2026
Texas A&M University has a proud history that stretches back to 1876 when The Agricultural and Mechanical College of Texas became the first public institution of higher learning in the state of Texas. Nestled in the heart of the Houston-Dallas-Austin triangle, Texas A&M...
Compliance Ranges Comparison

UC Santa Cruz Social Sciences







Texas A&M University






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

UC Santa Cruz Social Sciences

Texas A&M University
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.