Comparison Overview
The Graduate Center, City University of New York
The Graduate Center, City University of New York
365 Fifth Ave, New York, ny, 10016, US
Last Update: 28/02/2026
A graduate school of arts and sciences, a hub of some 30 centers of applied and theoretical research, and a platform for performance, discussion and debate, the Graduate Center is a community of students, scholars, and researchers dedicated to the idea that learning is ...
The Johns Hopkins University
3400 N Charles St, Mason Hall, Baltimore, MD, US, 21218-2688
Last Update: 02/04/2026
We are America’s first research university, founded in 1876 on the principle that by pursuing big ideas and sharing what we learn, we can make the world a better place. For more than 140 years, our faculty and students have worked side by side in pursuit of discoveries ...
Compliance Ranges Comparison
The Graduate Center, City University of New York
The Johns Hopkins University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The Graduate Center, City University of New York in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The Johns Hopkins University in 2026.
Incident History - The Graduate Center, City University of New York (X = Date, Y = Severity)
The Graduate Center, City University of New York cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Johns Hopkins University (X = Date, Y = Severity)
The Johns Hopkins University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Graduate Center, City University of New York
The Johns Hopkins 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.