Comparison Overview
Dilawri Group of Companies
Dilawri Group of Companies
87 Front St E, Toronto, Ontario, M5E 1B8, CA
Last Update: 26/02/2026
Privately owned and operated since 1985, today Dilawri continues to build on its history of excellence as Canada’s largest automotive group. The company's national network represents 38 of the world’s most beloved automotive brands at 83 franchised dealerships in Canada...
FORVIA
N/A
Last Update: 04/04/2026
FORVIA comprises the complementary technology and industrial strengths of Faurecia and HELLA. With over 249 industrial sites and 78 R&D centers, 150,000 people, including more than 15,000 engineers across 40+ countries, FORVIA provides a unique and comprehensive approac...
Compliance Ranges Comparison
Dilawri Group of Companies
FORVIA
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Dilawri Group of Companies in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for FORVIA in 2026.
Incident History - Dilawri Group of Companies (X = Date, Y = Severity)
Dilawri Group of Companies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FORVIA (X = Date, Y = Severity)
FORVIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Dilawri Group of Companies
FORVIA
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: *.*.