Comparison Overview
Land Rover Vancouver

Land Rover Vancouver
1730 Burrard Street, Vancouver, British Columbia, V6J 3G7, CA
Last Update: 13/12/2025
Land Rover Vancouver has been proudly serving the Vancouver, BC community since 2010 as a premier Land Rover Dealership specialising in New & Used Land Rover Vehicle Sales, Service and Parts. Dedicated to helping you find the perfect vehicle for you; whether it is new,...

Dana Incorporated
3939 Technology Drive, Maumee, 43537, US
Last Update: 02/04/2026
In a world of constant motion, life is about balance. At Dana, our balanced approach considers the people, products, and planet that sustain us all. For 120 years, we've been powering innovation to move our world. Today, over 25,000 Dana people, in more than 20 countr...
Compliance Ranges Comparison

Land Rover Vancouver







Dana Incorporated






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Land Rover Vancouver in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Dana Incorporated in 2026.
Incident History - Land Rover Vancouver (X = Date, Y = Severity)
Land Rover Vancouver cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dana Incorporated (X = Date, Y = Severity)
Dana Incorporated cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Land Rover Vancouver

Dana Incorporated
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: *.*.