Comparison Overview
FNX-INNOV
FNX-INNOV
433 Rue Chabanel O, Montréal, H2N 2J8, CA
Last Update: 03/03/2026
At FNX-INNOV, we strive every day to redefine engineering without any barriers. We are a Quebec-owned company that innovates through its integrated services from conception to execution. With our 1000 professionals and experts, we excel in cutting-edge sectors such as t...
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...
Compliance Ranges Comparison
FNX-INNOV
SNC-Lavalin
Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for FNX-INNOV in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for SNC-Lavalin in 2026.
Incident History - FNX-INNOV (X = Date, Y = Severity)
FNX-INNOV cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SNC-Lavalin (X = Date, Y = Severity)
SNC-Lavalin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
FNX-INNOV
SNC-Lavalin
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.