Comparison Overview
Tokio Marine
Tokio Marine
6/8 boulevard Haussmann, Paris, undefined, 75009, FR
Last Update: 12/03/2026
Filliale de Tokio Marine and Nichido Fire Insurance Co.Limited, la plus importante et la plus ancienne société d’assurances Non vie au Japon dans le domaine des risques d’entreprises et des risques Maritimes et Transports, nous développons et gérons les opérations d'a...
Helvetia Baloise Group
N/A
Last Update: 02/04/2026
Helvetia Baloise is the largest multi-line insurer in Switzerland and one of the leading insurance groups in Europe. Every day, more than 22,000 employees are committed to supporting around 13 million customers with insurance, pension and financial solutions – from priv...
Compliance Ranges Comparison
Tokio Marine
Helvetia Baloise Group
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Tokio Marine in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Helvetia Baloise Group in 2026.
Incident History - Tokio Marine (X = Date, Y = Severity)
Tokio Marine cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Helvetia Baloise Group (X = Date, Y = Severity)
Helvetia Baloise Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tokio Marine
Helvetia Baloise Group
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: *.*.