Comparison Overview
Tim Hortons - Middle East
Tim Hortons - Middle East
Riyadh, 99987, SA, Riyadh, 99987, SA
Last Update: 22/04/2026
Over the years, Tim Hortons has captured the hearts and taste buds of not only Canadians, but people all over the world, with classics like our Original Blend coffee and the signature Iced Capp®, along with a variety of inspired donuts including our ever popular Timbit...
The Coca-Cola Company
One Coca-Cola Plaza, Atlanta, 30313, US
Last Update: 06/07/2026
From our roots at the counter of a local Atlanta pharmacy, to our current portfolio of more than 200 beverages, The Coca-Cola Company is one of the most globally-recognized brands in the world. Today, our lineup features beloved beverage brands, including Coca-Cola, S...
Compliance Ranges Comparison
Tim Hortons - Middle East
The Coca-Cola Company
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Tim Hortons - Middle East in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
The Coca-Cola Company has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Tim Hortons - Middle East (X = Date, Y = Severity)
Tim Hortons - Middle East cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Coca-Cola Company (X = Date, Y = Severity)
The Coca-Cola Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tim Hortons - Middle East
The Coca-Cola Company
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: *.*.