Comparison Overview
Tecnológico de Monterrey
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 ...
McGill University
845 Sherbrooke Street West, Montreal, Qc, CA, H3A 2T5
Last Update: 01/04/2026
McGill University is one of Canada's best-known institutions of higher learning and one of the leading universities in the world. With students coming to McGill from some 150 countries, our student body is the most internationally diverse of any research-intensive unive...
Compliance Ranges Comparison
Tecnológico de Monterrey
McGill University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Tecnológico de Monterrey in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for McGill University in 2026.
Incident History - Tecnológico de Monterrey (X = Date, Y = Severity)
Tecnológico de Monterrey cyber incidents detection timeline including parent company and subsidiaries.
Incident History - McGill University (X = Date, Y = Severity)
McGill University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tecnológico de Monterrey
McGill University
FAQ
Latest Global CVEs
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in PhialsBasement KoboldCPP-MCP-Server 1.0.0. Affected by this issue is the function makeRequest of the file src/index.ts of the component BaseConfigSchema. Executing a manipulation of the argument apiUrl can lead to server-side request forgery. It is possible to launch the attack on the local host. The project was informed of the problem early through an issue report but has not responded yet.
A security flaw has been discovered in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this vulnerability is the function fs.readFileSync of the file src/index.ts of the component upload_document. Performing a manipulation of the argument File results in path traversal. Attacking locally is a requirement. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was identified in Nikolaibibo claude-comfyui-mcp 1.0.0. Affected is the function copyFileSync of the file src/tools/utils.ts of the component comfy_upload_image. Such manipulation of the argument image_path leads to path traversal. An attack has to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.