Comparison Overview
Boursorama
Boursorama
44 rue Traversière, BOULOGNE BILLANCOURT, FR
Last Update: 27/03/2026
Lancée en 1998, BoursoBank est un acteur pionnier et leader sur ses activités principales : la banque et l'information économique et financière en ligne. Avec un développement centré autour des nouvelles attentes des clients, simplicité et efficacité, mais aussi sécur...
Nomura
1-9-1 Nihonbashi, Tokyo, 103-8645, JP
Last Update: 15/09/2026
Nomura is a financial services group with an integrated global network. By connecting markets East & West, Nomura services the needs of individuals, institutions, corporates and governments through its four business divisions: Wealth Management, Investment Management, W...
Compliance Ranges Comparison
Boursorama
Nomura
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Boursorama in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Nomura in 2026.
Incident History - Boursorama (X = Date, Y = Severity)
Boursorama cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nomura (X = Date, Y = Severity)
Nomura cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Boursorama
Nomura
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.