Comparison Overview
Department of Civil and Environmental Engineering - University of Waterloo
Department of Civil and Environmental Engineering - University of Waterloo
200 University Avenue West, Waterloo, N2L 3G1, CA
Last Update: 01/03/2026
Welcome to one of the largest and most well-respected civil and environmental engineering departments in Canada. With 830 students enrolled in our undergraduate degree programs for architectural, civil, environmental and geological engineering, and 180 students in our ...
AECOM
13355 Noel Road, Suite 400, Dallas, Texas, US, 75240
Last Update: 01/04/2026
AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy, transportation and buildings. Our team...
Compliance Ranges Comparison
Department of Civil and Environmental Engineering - University of Waterloo
AECOM
Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Department of Civil and Environmental Engineering - University of Waterloo in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for AECOM in 2026.
Incident History - Department of Civil and Environmental Engineering - University of Waterloo (X = Date, Y = Severity)
Department of Civil and Environmental Engineering - University of Waterloo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AECOM (X = Date, Y = Severity)
AECOM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Department of Civil and Environmental Engineering - University of Waterloo
AECOM
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.