Comparison Overview
BMW Motorrad Belux
BMW Motorrad Belux
Lodderstraat, 16, Bornem, Belgique, 2880 , BE
Last Update: 07/12/2025
Bienvenue sur le compte Linkedin officiel de BMW Motorrad Belux. BMW Motorrad Belux se charge de l’importation, la promotion et la commercialisation de produits, pièces de rechange, vêtements et accessoires pour la marque BMW Motorrad à travers un réseau de 20 concessi...
Volkswagen
Berliner Ring 2, 38440 Wolfsburg, Wolfsburg, 38440, DE
Last Update: 26/06/2026
Volkswagen is a brand for the heart and for the people – likeable, great quality with trend-setting designs – from the T1 and the Beetle to the Golf and today’s ID. Buzz. We are carrying over Volkswagen’s traditional strengths into the new world of mobility. Carbon neut...
Compliance Ranges Comparison
BMW Motorrad Belux
Volkswagen
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for BMW Motorrad Belux in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Volkswagen in 2026.
Incident History - BMW Motorrad Belux (X = Date, Y = Severity)
BMW Motorrad Belux cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Volkswagen (X = Date, Y = Severity)
Volkswagen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BMW Motorrad Belux
Volkswagen
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: *.*.