Comparison Overview
Asahi Holdings Southeast Asia Sdn Bhd
Asahi Holdings Southeast Asia Sdn Bhd
Jalan Bukit Bintang, Kuala Lumpur, MY
Last Update: 02/04/2026
Asahi Holdings Southeast Asia (AHSEA) is a subsidiary of Asahi Group Holdings with leading market equity across Southeast Asia. Our presence covers a diverse range of beverages in various geographies including Malaysia, Singapore, Indonesia, Vietnam, Thailand, Myanmar, ...
GoTo Foods
5620 Glenridge Drive, Atlanta, GA, US, 30342
Last Update: 04/04/2026
Atlanta-based platform company GoTo Foods (formerly known as Focus Brands) is a leading developer of global multi-channel foodservice brands. As of December 28 , 2025, GoTo Foods, through its affiliate brands, is the franchisor and operator of over 7,300 restaurants, ca...
Compliance Ranges Comparison
Asahi Holdings Southeast Asia Sdn Bhd
GoTo Foods
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Asahi Holdings Southeast Asia Sdn Bhd in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for GoTo Foods in 2026.
Incident History - Asahi Holdings Southeast Asia Sdn Bhd (X = Date, Y = Severity)
Asahi Holdings Southeast Asia Sdn Bhd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GoTo Foods (X = Date, Y = Severity)
GoTo Foods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Asahi Holdings Southeast Asia Sdn Bhd
GoTo Foods
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: *.*.