Comparison Overview
Unimed Curitiba
Unimed Curitiba
Avenida Affonso Penna, 297, Curitiba, PR, 82530-280, BR
Last Update: 27/04/2026
A Unimed Curitiba é uma cooperativa de trabalho médico líder no mercado de assistência à saúde em sua área de atuação. Desde a sua criação, em agosto de 1971, busca agregar trabalho e dedicação para promover a acessibilidade de seus clientes a diversas especialidades m...
Massage Envy
14350 N. 87th St., Suite 200, Scottsdale, 85260, US
Last Update: 30/03/2026
Massage Envy is a leading wellness franchise providing professional massage, skin care, and assisted stretch services nationwide. Co-founded by a massage therapist in 2002, the brand’s mission is simple: make total body care accessible and affordable so people can feel ...
Compliance Ranges Comparison
Unimed Curitiba
Massage Envy
Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Unimed Curitiba in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Massage Envy in 2026.
Incident History - Unimed Curitiba (X = Date, Y = Severity)
Unimed Curitiba cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Massage Envy (X = Date, Y = Severity)
Massage Envy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Unimed Curitiba
Massage Envy
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: *.*.