Comparison Overview
Fleury Medicina e Saúde
Fleury Medicina e Saúde
Alameda Araguaia, 2400, São Paulo, SP, 06472-001, BR
Last Update: 07/02/2026
Desde 1926, o Fleury Medicina e Saúde, marca do Grupo Fleury, pauta sua atuação em excelência e acolhimento. Hoje, está presente em São Paulo e no Distrito Federal e é uma das mais respeitadas marcas de medicina e saúde do Brasil, atuando em prevenção, medicina diagnóst...
None
420 24th Ave SW, Norman, 73069, US
Last Update: 02/04/2026
Norman Smile Center is Norman's premier destination for all of your dental needs. Dentists Jamie Belknap, DDS, Donna Sparks, DDS, and Kristen Campbell, DDS, Norman OK, practice a full scope of general and cosmetic dentistry with expertise ranging from porcelain veneers ...
Compliance Ranges Comparison
Fleury Medicina e Saúde
None
Benchmark & Cyber Underwriting Signals
Incidents vs Health, Wellness & Fitness Industry Avg (This Year)
No incidents recorded for Fleury Medicina e Saúde in 2026.
Incidents vs Health, Wellness & Fitness Industry Avg (This Year)
No incidents recorded for None in 2026.
Incident History - Fleury Medicina e Saúde (X = Date, Y = Severity)
Fleury Medicina e Saúde cyber incidents detection timeline including parent company and subsidiaries.
Incident History - None (X = Date, Y = Severity)
None cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fleury Medicina e Saúde
None
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: *.*.