Comparison Overview
Havan
Havan
Rodovia Antonio Heil, 191, Brusque, SC, undefined, BR
Last Update: 25/02/2026
Somos uma gigante do varejo com o propósito de promover o desenvolvimento econômico e social do Brasil. Nossa história teve início em 1986 em Brusque (SC), com uma loja de 45 m² e apenas um funcionário. Hoje já são quase 200 megalojas espalhadas pelo Brasil e mais de 20...
Riachuelo
Rua Lemos Monteiro, 120, Butantã, São Paulo, São Paulo, 05501-050, BR
Last Update: 01/02/2026
Sabe aquele sentimento de estar na empresa certa, na função certa, com muitos desafios, mas com ainda mais oportunidades? É isso o que valorizamos por aqui. Por isso, há mais de 76 anos a gente constrói a nossa história com cada RCHLOVER. A gente tem uma fábrica, em N...
Compliance Ranges Comparison
Havan
Riachuelo
Benchmark & Cyber Underwriting Signals
Incidents vs Comércio varejista Industry Avg (This Year)
No incidents recorded for Havan in 2026.
Incidents vs Comércio varejista Industry Avg (This Year)
No incidents recorded for Riachuelo in 2026.
Incident History - Havan (X = Date, Y = Severity)
Havan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Riachuelo (X = Date, Y = Severity)
Riachuelo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Havan
Riachuelo
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: *.*.