Comparison Overview
Inspection générale Groupe BPCE

Inspection générale Groupe BPCE
110, Avenue de France, Paris, 75013, FR
Last Update: 01/01/2026
Rattachée au plus haut niveau du Groupe BPCE, l'Inspection générale assure le contrôle périodique de l'organisation, notamment du dispositif de contrôle interne, de la gestion et de la situation financière des établissements du Groupe, anime et pilote la Filière Audit d...

Maybank
100 Jalan Tun Perak, Kuala Lumpur, Wilayah Persekutuan, MY, 50050
Last Update: 02/04/2026
Maybank Group is the leading financial services provider in Malaysia catering to the needs of consumers, investors, entrepreneurs, non-profit organisations and corporations. The Group, which has expanded internationally, has the largest network among Malaysian banks of ...
Compliance Ranges Comparison

Inspection générale Groupe BPCE







Maybank






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Inspection générale Groupe BPCE in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Maybank in 2026.
Incident History - Inspection générale Groupe BPCE (X = Date, Y = Severity)
Inspection générale Groupe BPCE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Maybank (X = Date, Y = Severity)
Maybank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Inspection générale Groupe BPCE

Maybank
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