Comparison Overview
Laborie OBGYN & Neonatal Health
Laborie OBGYN & Neonatal Health
747 West 4170 South, Murray, 84123, US
Last Update: 21/11/2025
Clinical Innovations was acquired by Laborie in Feb 2020 and forms a new business unit specifically focused on medical device solutions in Obstetrics, Gynecology and Neonatal Health. We are passionate about helping every mother and every newborn and to ensure they go ho...
BD
1 Becton Drive, Franklin Lakes, 07417, US
Last Update: 01/04/2026
BD is one of the largest global medical technology companies in the world and is advancing the world of health™ by improving medical discovery, diagnostics and the delivery of care. The company supports the heroes on the frontlines of health care by developing innovativ...
Compliance Ranges Comparison
Laborie OBGYN & Neonatal Health
BD
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Laborie OBGYN & Neonatal Health in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for BD in 2026.
Incident History - Laborie OBGYN & Neonatal Health (X = Date, Y = Severity)
Laborie OBGYN & Neonatal Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BD (X = Date, Y = Severity)
BD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Laborie OBGYN & Neonatal Health
BD
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: *.*.