Comparison Overview
TÜV Rheinland Medical Devices
TÜV Rheinland Medical Devices
N/A
Last Update: 22/04/2026
Follow us and keep up to date with the dynamic regulatory environment for medical devices and in vitro diagnostics. For more than 150 years, TÜV Rheinland has stood for quality, safety, and efficiency in connection with people, the environment, and technology. As an i...
B. Braun Group
Carl-Braun-Straße 1, Melsungen, DE, 34212
Last Update: 01/04/2026
As a leading medical technology company, B. Braun protects and improves the health of people around the world. For more than 185 years, the family-owned company has been accelerating progress in health care with pioneering spirit and groundbreaking contributions. This i...
Compliance Ranges Comparison
TÜV Rheinland Medical Devices
B. Braun Group
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for TÜV Rheinland Medical Devices in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for B. Braun Group in 2026.
Incident History - TÜV Rheinland Medical Devices (X = Date, Y = Severity)
TÜV Rheinland Medical Devices cyber incidents detection timeline including parent company and subsidiaries.
Incident History - B. Braun Group (X = Date, Y = Severity)
B. Braun Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TÜV Rheinland Medical Devices
B. Braun Group
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: *.*.