Comparison Overview
Acosta Bentonville
Acosta Bentonville
4204 S Pinnacle Hills Pkwy, Rogers, Arkansas, 72758, US
Last Update: 02/04/2026
Acosta's experts stand at the forefront of retail, crafting headquarter selling and omnichannel growth strategies that enable leading brands throughout North America and Europe to excel in their categories. Since 1927, Acosta has cultivated trusted relationships and mas...
Grupo Casas Bahia
Rua Flórida 1970, São Paulo, SP, BR, 04575-030
Last Update: 01/04/2026
Mais do que varejo, somos um ecossistema que conecta produtos, serviços, crédito e logística com dedicação total! Estamos presentes na mente, no coração e na casa de milhões de brasileiros, com um portfólio de marcas que há décadas faz parte da vida das pessoas: Casas...
Compliance Ranges Comparison
Acosta Bentonville
Grupo Casas Bahia
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Acosta Bentonville in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Grupo Casas Bahia in 2026.
Incident History - Acosta Bentonville (X = Date, Y = Severity)
Acosta Bentonville cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Grupo Casas Bahia (X = Date, Y = Severity)
Grupo Casas Bahia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Acosta Bentonville
Grupo Casas Bahia
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: *.*.