Comparison Overview
Rumah
Rumah
Centro, Balneário Camboriú, BR
Last Update: 02/04/2026
Fundada em Junho de 2015, a Rumah é uma loja online especializada em artigos de decoração e itens para a casa, entregando seus produtos para o Brasil inteiro. Com um portfólio grande e variado, a Rumah proporciona diversas opções para seus clientes em várias categorias....
Inditex
Avda. de la Diputación s/n, Arteixo, 15143, ES
Last Update: 05/06/2026
What is Inditex? Inditex comprises seven brands: Zara, Pull&Bear, Massimo Dutti, Bershka, Stradivarius, Oysho and Zara Home. We sell in 213 markets through our online platforms and our over 5.800 stores. But… What is Inditex? We are the clothes you choose to wear, th...
Compliance Ranges Comparison
Rumah
Inditex
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Rumah in 2026.
Incidents vs Retail Industry Avg (This Year)
Inditex has 277.36% more incidents than the average of all companies with at least one recorded incident.
Incident History - Rumah (X = Date, Y = Severity)
Rumah cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Inditex (X = Date, Y = Severity)
Inditex cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Rumah
Inditex
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: *.*.