Comparison Overview
BNP Paribas

BNP Paribas
16 boulevard des Italiens, Paris, FR, 75009
Last Update: 12/09/2026
BNP Paribas is a leading bank in Europe with an international reach. It has a presence in 64 countries, with more than 178,000 employees, including more than 144,000 in Europe. BNP Paribas holds leading positions in its three major operating divisions: ⚆ Commercial, P...

alrajhi bank
King Fahad Branch Road, Al Rajhi Tower, Riyadh, Riyadh Province, SA, 11411
Last Update: 04/05/2026
Founded in 1957, Al Rajhi Bank is one of the largest Islamic banks in the world with total assets of SR 384 billion (US$ 102 billion), a paid up capital of SR 25 billion (US$ 6.66 billion) and an employee base of over 9,600 associates. With over 58 years of experience i...
Compliance Ranges Comparison

BNP Paribas







alrajhi bank






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas in 2026.
Incidents vs Banking Industry Avg (This Year)
alrajhi bank has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BNP Paribas (X = Date, Y = Severity)
BNP Paribas cyber incidents detection timeline including parent company and subsidiaries.
Incident History - alrajhi bank (X = Date, Y = Severity)
alrajhi bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BNP Paribas

alrajhi bank
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout