Comparison Overview
foodora
foodora
undefined, Berlin, undefined, undefined, DE
Last Update: 13/11/2025
At foodora, we believe that freedom can be delivered. To our customers, and to our teams: in foodora, you have the freedom to create your own journey, choose to create impact and make a difference every day. You'll be part of a team of +2000 people in seven countries a...
Keurig Dr Pepper Inc.
53 South Ave, Burlington, 01803, US
Last Update: 01/04/2026
Keurig Dr Pepper (KDP) is a leading beverage company in North America, with annual revenue in excess of $14.1 billion and nearly 28,000 employees. KDP holds leadership positions in soft drinks, specialty coffee and tea, water, juice and juice drinks and mixers, and mark...
Compliance Ranges Comparison
foodora
Keurig Dr Pepper Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for foodora in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Keurig Dr Pepper Inc. in 2026.
Incident History - foodora (X = Date, Y = Severity)
foodora cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Keurig Dr Pepper Inc. (X = Date, Y = Severity)
Keurig Dr Pepper Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
foodora
Keurig Dr Pepper Inc.
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: *.*.