Comparison Overview
Indomaret Group
Indomaret Group
Jalan Pantai Indah Kapuk Boulevard No.1, Jakarta Utara, 14470, ID
Last Update: 02/04/2026
Originated from the idea to facilitate the provision of employees’ basic daily needs, a store, known as Indomaret, was established in 1988. As the store developed, the Company were interested to further explore and understand the consumers’ various needs and shopping be...
Toys"R"Us
Parsippany, 07054, US
Last Update: 01/04/2026
Toys“R”Us is a beloved brand known all around the world—and we know how to have fun! For over 70 years we've been the toy authority and ambassadors of all things play. Our new vision looks beyond traditional retail for a re-imagined, immersive experience for kids of all...
Compliance Ranges Comparison
Indomaret Group
Toys"R"Us
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Indomaret Group in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Toys"R"Us in 2026.
Incident History - Indomaret Group (X = Date, Y = Severity)
Indomaret Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Toys"R"Us (X = Date, Y = Severity)
Toys"R"Us cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Indomaret Group
Toys"R"Us
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: *.*.