Comparison Overview
Olimpica S.A.
Olimpica S.A.
53 # 46-192, Barranquilla, CO
Last Update: 20/02/2026
En Almacenes Olímpica, nos posicionamos como una de las compañías líderes en la comercialización de productos de consumo masivo de óptima calidad. A través de nuestra extensa red privada de Droguerías, Superdroguerías, Supertiendas y Superalmacenes, estamos dedicados a ...
PetSmart
19601 N. 27th Avenue, Phoenix, 85027, US
Last Update: 29/03/2026
At PetSmart, we’ll do Anything for Pets. ❤️🐾 And the people who love them! Because we’re those people, too. Pets inspire and motivate us to bring our best selves to work each day. Our associates are devoted to ensuring that pets’ lives are happy and healthy. So, natura...
Compliance Ranges Comparison
Olimpica S.A.
PetSmart
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Olimpica S.A. in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for PetSmart in 2026.
Incident History - Olimpica S.A. (X = Date, Y = Severity)
Olimpica S.A. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PetSmart (X = Date, Y = Severity)
PetSmart cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Olimpica S.A.
PetSmart
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: *.*.