Comparison Overview
a+ Medicina Diagnóstica

a+ Medicina Diagnóstica
undefined, undefined, undefined, undefined, BR
Last Update: 25/11/2025
A a+ Medicina Diagnóstica é uma marca do Grupo Fleury que oferece excelência e bom atendimento para os clientes de São Paulo, Paraná, Bahia e Pernambuco. Nascida há 5 anos da união de várias marcas adquirias pelo Grupo Fleury, a a+ tem um portfólio composto por exames d...

Smart Fit
Avenida Paulista 1294, São Paulo, BR
Last Update: 01/04/2026
Somos o Grupo Smart Fit, a força que ativa o seu potencial. Um ecossistema em constante evolução que une tecnologia, propósito e performance para transformar o fitness, e a vida das pessoas, em movimento real. Com mais de 22 mil colaboradores e colaboradoras em 16 país...
Compliance Ranges Comparison

a+ Medicina Diagnóstica







Smart Fit






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for a+ Medicina Diagnóstica in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Smart Fit in 2026.
Incident History - a+ Medicina Diagnóstica (X = Date, Y = Severity)
a+ Medicina Diagnóstica cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Smart Fit (X = Date, Y = Severity)
Smart Fit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

a+ Medicina Diagnóstica

Smart Fit
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: *.*.