Comparison Overview
bibigo Europe (CJ Foods)
bibigo Europe (CJ Foods)
Siemensstraße , 13-17, Nidderau, Hesse, DE, 61130
Last Update: 02/04/2026
CJ Foods Shares Korean Flavor! CJ Food Europe is an European subsidiary of CJ CheilJedang, that is in charge of the food manufacturing and trading for European market . CJ CheilJedang has led the development of the Korean food industry for the past 60 years, and cont...
Krispy Kreme
2116 Hawkins St, Charlotte, North Carolina, US, 28203
Last Update: 27/05/2026
Headquartered in Charlotte, N.C., Krispy Kreme is one of the most beloved and well-known sweet treat brands in the world. Our iconic Original Glazed® doughnut is universally recognized for its hot-off-the-line, melt-in-your-mouth experience. Krispy Kreme operates in mor...
Compliance Ranges Comparison
bibigo Europe (CJ Foods)
Krispy Kreme
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for bibigo Europe (CJ Foods) in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
Krispy Kreme has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - bibigo Europe (CJ Foods) (X = Date, Y = Severity)
bibigo Europe (CJ Foods) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Krispy Kreme (X = Date, Y = Severity)
Krispy Kreme cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
bibigo Europe (CJ Foods)
Krispy Kreme
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: *.*.