Comparison Overview
Weinmann
Weinmann
undefined, undefined, RS, undefined, BR
Last Update: 02/04/2026
Com mais de 80 anos de tradição e referência no Rio Grande do Sul, o Weinmann é a marca gaúcha do Grupo Fleury. Para usufruir os serviços de uma marca especialista, envolvente e contemporânea, os clientes contam com unidades distribuídas em Porto Alegre, Grande Porto Al...
LA Fitness
PO Box 55088, Irvine, 92619, US
Last Update: 29/03/2026
LA Fitness is a privately owned fitness club chain. LA Fitness has hundreds of health clubs gyms and millions of members across US and Canada. In an industry often equated with fad and fashion, LA Fitness has steadily increased its presence by focusing on the one lifelo...
Compliance Ranges Comparison
Weinmann
LA Fitness
Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Weinmann in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for LA Fitness in 2026.
Incident History - Weinmann (X = Date, Y = Severity)
Weinmann cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LA Fitness (X = Date, Y = Severity)
LA Fitness cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Weinmann
LA 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: *.*.