Comparison Overview
Allianz Partners, Health
Allianz Partners, Health
15 Joyce Way, Dublin, Dublin 12, IE
Last Update: 17/03/2026
Welcome to our Allianz Partners, Health LinkedIn page. Connect with us to engage and network with industry leaders, and get the latest trends in health innovation and solutions. Allianz Partners, Health offers health, life and disability insurance as well as a wide ra...
Manulife
200 Bloor St E, Toronto, M4W, CA
Last Update: 29/06/2026
Manulife is a leading international financial services group that helps people make their decisions easier and lives better. With our global headquarters in Toronto, we operate as Manulife across our offices in Canada, Asia, and Europe, and primarily as John Hancock in ...
Compliance Ranges Comparison
Allianz Partners, Health
Manulife
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Allianz Partners, Health in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Manulife in 2026.
Incident History - Allianz Partners, Health (X = Date, Y = Severity)
Allianz Partners, Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Manulife (X = Date, Y = Severity)
Manulife cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Allianz Partners, Health
Manulife
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: *.*.