Comparison Overview
Too Good To Go
Too Good To Go
Landskronagade 66, København Ø, Capital Region, 2100, DK
Last Update: 04/04/2026
Too Good To Go is a certified B Corp social impact company that connects users with partner stores to rescue unsold food and stop it from going to waste. With 85 million registered users and 150,000 active partners in 17 countries across Europe and North America, Too Go...
Bureau Veritas Group
4 Place des Saisons, Paris, 92400, FR
Last Update: 03/04/2026
Bureau Veritas is a world leader in Testing, Inspection and Certification. Our mission is at the heart of key challenges: quality, health and safety, environmental protection and social responsibility. Through our wide range of expertise, impartiality and independence, ...
Compliance Ranges Comparison
Too Good To Go
Bureau Veritas Group
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Too Good To Go in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Bureau Veritas Group in 2026.
Incident History - Too Good To Go (X = Date, Y = Severity)
Too Good To Go cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bureau Veritas Group (X = Date, Y = Severity)
Bureau Veritas Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Too Good To Go
Bureau Veritas Group
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: *.*.