Comparison Overview
Macromedia University of Applied Sciences

Macromedia University of Applied Sciences
Sandstraße 9, München, DE, 80335
Last Update: 01/03/2026
Wir sind eine bundesweit tätige, private Hochschule mit über 5.000 Studierenden und 140 Professorinnen und Professoren. Campus gibt es in München, Stuttgart, Freiburg, Frankfurt, Köln, Hamburg, Leipzig und Berlin. Unterrichtssprachen sind Deutsch und Englisch. Zum Por...

Kansas State University
119 Anderson Hall, Manhattan, KS, US, 66506
Last Update: 02/04/2026
Kansas State University, often referred to as K-State, is an institution of higher learning located in Manhattan, Kansas, in the United States. A branch campus, including the College of Technology and Aviation, is located in Salina, Kansas. A third campus, K-State Ola...
Compliance Ranges Comparison

Macromedia University of Applied Sciences







Kansas State University






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

Macromedia University of Applied Sciences

Kansas State 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.