Comparison Overview
Sustainability and Health Research Hub of the Technological University Dublin
Sustainability and Health Research Hub of the Technological University Dublin
Environmental Sustainability and Health Intitute. Technological University Dublin, Dublin, D07 H6K8, IE
Last Update: 29/01/2026
The SHRH is an inter-disciplinary & cross-sectoral research hub dedicated to research between the environment &health. The SHRH (under its previous denomination ESHI) was funded under PRTLI Cycle 5
Tecnológico de Monterrey
Ave. Eugenio Garza Sada 2501 Sur, Colonia Tecnológico, Monterrey, nuevo león, MX, 64849
Last Update: 02/04/2026
The Tecnológico de Monterrey is a private university system with 33 campuses in 26 cities in Mexico, which serves more than 96,000 students in its high school, undergraduate and graduate programs. It also has liaison offices in 12 countries. Through the promotion of ...
Compliance Ranges Comparison
Sustainability and Health Research Hub of the Technological University Dublin
Tecnológico de Monterrey
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Sustainability and Health Research Hub of the Technological University Dublin in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Tecnológico de Monterrey in 2026.
Incident History - Sustainability and Health Research Hub of the Technological University Dublin (X = Date, Y = Severity)
Sustainability and Health Research Hub of the Technological University Dublin cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tecnológico de Monterrey (X = Date, Y = Severity)
Tecnológico de Monterrey cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sustainability and Health Research Hub of the Technological University Dublin
Tecnológico de Monterrey
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.