Comparison Overview
Amazon MX Player
Amazon MX Player
Andheri Kurla Road, Mumbai, 400093, IN
Last Update: 10/03/2026
Your Premier Streaming Destination! With over 236 million monthly active users and 1 billion+ downloads, we offer advertisers innovative solutions to drive brand awareness and engagement. Our premium ad units seamlessly integrate into popular content streams, maximizin...
Dave & Buster's Inc.
1221 S Belt Line Rd, Coppell, Texas, 75019, US
Last Update: 31/03/2026
Welcome to Dave & Buster's, the ONLY place to Eat, Drink, Play & Watch Sports®, all under one roof! Here, you can immerse yourself in a world of excitement, from our Million Dollar Midway, packed with the hottest arcade games, to our mouth-watering, chef-crafted creatio...
Compliance Ranges Comparison
Amazon MX Player
Dave & Buster's Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Amazon MX Player in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Dave & Buster's Inc. in 2026.
Incident History - Amazon MX Player (X = Date, Y = Severity)
Amazon MX Player cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dave & Buster's Inc. (X = Date, Y = Severity)
Dave & Buster's Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Amazon MX Player
Dave & Buster's Inc.
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: *.*.