Comparison Overview
Alkhorayef Group
Alkhorayef Group
Al Kharj Road, None, Riyadh, None, SA, None
Last Update: 25/01/2026
Since our foundation in 1957, Alkhorayef Group has become a strong and successful diversified business. We are leaders in Saudi Arabia and in our region, enjoying a strong reputation for quality and service. We also have a growing international presence, operating in ov...
Tata Group
Bombay House, Mumbai, 400001, IN
Last Update: 28/06/2026
Founded by Jamsetji Tata in 1868, the Tata group is a global enterprise headquartered in India. The group operates in more than 100 countries across six continents with a mission 'To improve the quality of life of the communities we serve globally, through long-term sta...
Compliance Ranges Comparison
Alkhorayef Group
Tata Group
Benchmark & Cyber Underwriting Signals
Incidents vs Executive Offices Industry Avg (This Year)
No incidents recorded for Alkhorayef Group in 2026.
Incidents vs Executive Offices Industry Avg (This Year)
Tata Group has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Alkhorayef Group (X = Date, Y = Severity)
Alkhorayef Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tata Group (X = Date, Y = Severity)
Tata Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alkhorayef Group
Tata Group
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: *.*.