Comparison Overview
Raya Gulf CX KSA
Raya Gulf CX KSA
Olaya Street, Riyadh Region, 12244, SA
Last Update: 02/04/2026
We build, integrate and deliver the best customer experience solutions from around the world. By customizing our packages to meet your specific goals and business requirements, we’re able to operate omni-channel, world class customer experience centers on your behalf. ...
Bain & Company
131 Dartmouth Street, Boston, MA, US, 02116
Last Update: 14/04/2026
Bain & Company is a global consultancy that helps the world’s most ambitious change makers define the future. Across 65 cities in 40 countries, we work alongside our clients as one team with a shared ambition to achieve extraordinary results, outperform the competitio...
Compliance Ranges Comparison
Raya Gulf CX KSA
Bain & Company
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Raya Gulf CX KSA in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Bain & Company has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Raya Gulf CX KSA (X = Date, Y = Severity)
Raya Gulf CX KSA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bain & Company (X = Date, Y = Severity)
Bain & Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Raya Gulf CX KSA
Bain & Company
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: *.*.