Comparison Overview
ESTS

ESTS
10 Anson Road, 27-18 International Plaza, Singapore, Singapore, SG
Last Update: 19/02/2026
Founded in 2013, ESTS (Extensive Standard Technical Services Co., Ltd.) is a global certification body and audit firm, with operators spanning Asia, Europe and North America. ESTS services mainly include three parts: certifications, audits/verification, and innovative ...

HelloFresh
Prinzenstraße 89, Berlin, 10969, DE
Last Update: 02/04/2026
HelloFresh is on a mission to change the way people eat, forever! From our 2011 founding in Europe’s vibrant tech hub Berlin, we’re evolving from the world’s leading meal kit company to the world's leading food solutions group. We delivered 243.3 million meals and reac...
Compliance Ranges Comparison

ESTS







HelloFresh






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for ESTS in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for HelloFresh in 2026.
Incident History - ESTS (X = Date, Y = Severity)
ESTS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HelloFresh (X = Date, Y = Severity)
HelloFresh cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ESTS

HelloFresh
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: *.*.