Comparison Overview
alrajhi bank Jordan
alrajhi bank Jordan
Abdel Hameed Sharaf, Amman , 11118, JO
Last Update: 14/03/2026
مصرف الراجحي هو أحد رواد الخدمات المصرفية في العالم بخبرة تمتد لأكثر من 50 عاماً في مجال الأعمال المصرفية والاستثمارية
Emirates NBD
Baniyas Road, Opp Dubai Creek Tower, Deira, Dubai, AE
Last Update: 02/04/2026
About Emirates NBD Emirates NBD (DFM: Emirates NBD) is a leading banking group in the MENAT (Middle East, North Africa and Türkiye) region with a presence in 13 countries, serving over 20 million customers. As at 30th September 2023, total assets were AED 836 billion,...
Compliance Ranges Comparison
alrajhi bank Jordan
Emirates NBD
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for alrajhi bank Jordan in 2026.
Incidents vs Banking Industry Avg (This Year)
Emirates NBD has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - alrajhi bank Jordan (X = Date, Y = Severity)
alrajhi bank Jordan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Emirates NBD (X = Date, Y = Severity)
Emirates NBD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
alrajhi bank Jordan
Emirates NBD
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: *.*.