Comparison Overview
Rohatyn Center for Global Affairs at Middlebury College

Rohatyn Center for Global Affairs at Middlebury College
Middlebury , 05753, US
Last Update: 07/02/2026
Through a diverse set of programs and events, the Rohatyn Center for Global Affairs (RCGA) reaches across boundaries of language, culture, and geography to engage students’ capacity for rigorous analysis and independent thought in a rapidly changing world. The RCGA The...

Northwestern University
633 Clark St, Evanston, IL, US, 60208
Last Update: 02/04/2026
Northwestern is one of the nation’s premier research universities, combining innovative teaching and pioneering research in a highly collaborative, multidisciplinary, and diverse environment. Northwestern provides both students and faculty exceptional opportunities for ...
Compliance Ranges Comparison

Rohatyn Center for Global Affairs at Middlebury College







Northwestern University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Rohatyn Center for Global Affairs at Middlebury College in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Northwestern University in 2026.
Incident History - Rohatyn Center for Global Affairs at Middlebury College (X = Date, Y = Severity)
Rohatyn Center for Global Affairs at Middlebury College cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Northwestern University (X = Date, Y = Severity)
Northwestern University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Rohatyn Center for Global Affairs at Middlebury College

Northwestern University
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.