Comparison Overview
Unimed Paranavaí
Unimed Paranavaí
Avenida Rio Grande do Norte 1428, Paranavaí, 87701-020, BR
Last Update: 24/11/2025
O início Por uma iniciativa de um grupo de 53 Médicos, há mais de 35 anos (desde 11 de Agosto 1988) foi fundada a Unimed de Paranavaí, com o firme propósito de retirar os pacientes das filas do sistema público de saúde para serem atendidos em consultórios particulares ...
Gold's Gym
5420 Lyndon B Johnson Fwy, Suite 300, Dallas, Texas, US, 75240
Last Update: 01/04/2026
Gold’s Gym has been the world’s trusted fitness authority since 1965. From its beginning as a small gym in Venice, California, Gold’s Gym has grown into a global icon with more than 700 locations serving 3 million people across six continents each day. Whether you are...
Compliance Ranges Comparison
Unimed Paranavaí
Gold's Gym
Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Unimed Paranavaí in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Gold's Gym in 2026.
Incident History - Unimed Paranavaí (X = Date, Y = Severity)
Unimed Paranavaí cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Gold's Gym (X = Date, Y = Severity)
Gold's Gym cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Unimed Paranavaí
Gold's Gym
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: *.*.