Comparison Overview
BEA Sensors Europe
BEA Sensors Europe
Liège science park, Allée des Noisetiers, 5, Angleur, BE, 4031
Last Update: 23/12/2025
BEA is a leading manufacturer of sensing solutions for automatic doors systems. The company was founded in 1965 and its headquarters are located in Liège, Belgium. BEA also has offices in the United States, Japan and China and our products can be found across the globe....
Vertiv
505 N. Cleveland Ave., Westerville, Columbus, OH, US, 43082
Last Update: 01/04/2026
Vertiv is a global leader in critical digital infrastructure for applications in data centers, communication networks, and commercial and industrial environments. As businesses, industries, and communities become more connected, we pioneer and deliver end-to-end power ...
Compliance Ranges Comparison
BEA Sensors Europe
Vertiv
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for BEA Sensors Europe in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Vertiv in 2026.
Incident History - BEA Sensors Europe (X = Date, Y = Severity)
BEA Sensors Europe cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vertiv (X = Date, Y = Severity)
Vertiv cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BEA Sensors Europe
Vertiv
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: *.*.