Comparison Overview
Starbucks Mexico
Starbucks Mexico
N/A
Last Update: 07/03/2026
Empresa líder de cafeterías en México, dedicada a la venta de café en grano, bebidas y alimentos con altos estándares de calidad. La primer tienda en México abrió sus puertas el 6 de septiembre de 2002 sobre la Avenida Paseo de la Reforma, actualmente contamos con alred...
Rentokil Terminix
N/A
Last Update: 01/04/2026
The Rentokil and Terminix family of brands have come together to form the world’s leading pest control company. With our shared vision, we’ll be expanding our products, services, and technology. And with our combined resources, we’ll do more to power innovation and deve...
Compliance Ranges Comparison
Starbucks Mexico
Rentokil Terminix
Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Starbucks Mexico in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Rentokil Terminix in 2026.
Incident History - Starbucks Mexico (X = Date, Y = Severity)
Starbucks Mexico cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rentokil Terminix (X = Date, Y = Severity)
Rentokil Terminix cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Starbucks Mexico
Rentokil Terminix
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: *.*.