Comparison Overview
SNC-Lavalin

SNC-Lavalin
455 René-Lévesque Blvd West, Montreal, H2Z 1Z3, CA
Last Update: 03/04/2026
SNC Lavalin is now AtkinsRéalis. Please follow AtkinsRéalis on LinkedIn. We are a world-class engineering services and nuclear organization. We connect people, data and technology to transform the world’s infrastructure and energy systems. Together, with our industry...

Parsons Corporation
14291 Park Meadow Dr, Chantilly, Virginia, US, 20151
Last Update: 13/09/2026
Founded in 1944, Parsons Corporation, a digitally enabled solutions provider, is focused on creating the future of the defense, intelligence, and critical infrastructure markets. From Earth to outer space, we deliver tomorrow’s solutions today. Equipped with the capabil...
Compliance Ranges Comparison

SNC-Lavalin







Parsons Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for SNC-Lavalin in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Parsons Corporation in 2026.
Incident History - SNC-Lavalin (X = Date, Y = Severity)
SNC-Lavalin cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Parsons Corporation (X = Date, Y = Severity)
Parsons Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SNC-Lavalin

Parsons Corporation
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)