Comparison Overview
Squadron Medical Ltd.
Squadron Medical Ltd.
Greaves Close, Chesterfield, Derbyshire,, S44 5FB (Sat Nav S44 5HN), GB
Last Update: 21/04/2026
We are the UK’s premier provider of third party logistic supplychain services to the healthcare sector. Renowned warehousing and distribution capability that delivers world class just-in-time theatre re-supply everyday across the country Our philosophy is simple, its y...
Boston Scientific
100 Boston Scientific Way, Marlborough, 01752, US
Last Update: 01/04/2026
Boston Scientific transforms lives through innovative medical technologies that improve the health of patients around the world. As a global medical technology leader for more than 40 years, we advance science for life by providing a broad range of high-performance solu...
Compliance Ranges Comparison
Squadron Medical Ltd.
Boston Scientific
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Squadron Medical Ltd. in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Boston Scientific has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Squadron Medical Ltd. (X = Date, Y = Severity)
Squadron Medical Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Boston Scientific (X = Date, Y = Severity)
Boston Scientific cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Squadron Medical Ltd.
Boston Scientific
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: *.*.