Comparison Overview
BNP Paribas in Switzerland
BNP Paribas in Switzerland
Place de Hollande, 2, Genève, undefined, Ch-1204, CH
Last Update: 23/02/2026
Dedicated to Corporates, institutions and private clients, BNP Paribas (Suisse) SA is a leading European bank in Switzerland based in Geneva, Zurich & Lugano. Active in Switzerland since 1872, we aim to be the preferred partner & a reference to our clients. We support...
Banque Misr
151 Mohamed Farid st.,Cairo Egypt, Cairo, EG
Last Update: 02/04/2026
Banque Misr (BM) was established in 1920 by the pioneer economist and financial expert Mohamed Talaat Harb Pasha, who spearheaded the concept of investing in national savings and directing them toward economic and social development. Thus, Banque Misr was established as...
Compliance Ranges Comparison
BNP Paribas in Switzerland
Banque Misr
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas in Switzerland in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banque Misr in 2026.
Incident History - BNP Paribas in Switzerland (X = Date, Y = Severity)
BNP Paribas in Switzerland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banque Misr (X = Date, Y = Severity)
Banque Misr cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BNP Paribas in Switzerland
Banque Misr
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: *.*.