Comparison Overview
Unimed Sergipe
Unimed Sergipe
Rua Socorro, 100, São José, Aracaju, Aracaju, Sergipe 49015300, BR
Last Update: 27/04/2026
A Unimed Sergipe Cooperativa de Trabalho Médico nasceu em 19 de novembro de 1984, fruto da visão empreendedora e da organização de alguns médicos sergipanos, como Dr. Ailton Pita Falcão (in memoriam), primeiro presidente da organização entre os anos de 1984 e 1998. Após...
Planet Fitness
Hampton, 03842, US
Last Update: 01/04/2026
Planet Fitness is taking the fitness industry by storm! Enhancing people’s lives with an affordable, high-quality fitness experience requires a team of inspiring, motivated and fun-loving go-getters. As one of the largest and fastest-growing franchisors and operators ...
Compliance Ranges Comparison
Unimed Sergipe
Planet Fitness
Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Unimed Sergipe in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Planet Fitness in 2026.
Incident History - Unimed Sergipe (X = Date, Y = Severity)
Unimed Sergipe cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Planet Fitness (X = Date, Y = Severity)
Planet Fitness cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Unimed Sergipe
Planet Fitness
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: *.*.