Comparison Overview
Freiburg Medical Laboratory
Freiburg Medical Laboratory
Dubai, AE
Last Update: 29/04/2026
Centrally located in Dubai, the pioneering company started its operations in late 2002 by the University Hospital Freiburg together with local partners, the Al Abbas Group. Since 2013, FML is a member of Synlab, the largest laboratory diagnostics provider in Europe. FML...
Dasa
Av das Nações Unidas 7815, São Paulo, 05425-070, BR
Last Update: 04/04/2026
A Dasa é uma das maiores empresas de saúde do mundo, líder em medicina diagnóstica no Brasil. Trabalha para transformar sua especialização, alcance e escala em acesso à saúde de qualidade e cuidado humanizado. A empresa faz parte da vida de mais de 20 milhões de pessoa...
Compliance Ranges Comparison
Freiburg Medical Laboratory
Dasa
Benchmark & Cyber Underwriting Signals
Incidents vs Medical and Diagnostic Laboratories Industry Avg (This Year)
No incidents recorded for Freiburg Medical Laboratory in 2026.
Incidents vs Medical and Diagnostic Laboratories Industry Avg (This Year)
No incidents recorded for Dasa in 2026.
Incident History - Freiburg Medical Laboratory (X = Date, Y = Severity)
Freiburg Medical Laboratory cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dasa (X = Date, Y = Severity)
Dasa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Freiburg Medical Laboratory
Dasa
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: *.*.