Comparison Overview
Amplifon Hearing Health Care
Amplifon Hearing Health Care
Fifth Street Towers, 150 S 5th St, Suite 2300, Minneapolis, Minnesota, US, 55402
Last Update: 13/02/2026
Amplifon Hearing Health Care makes it easy for health plans to provide high-quality, affordable hearing health care to members. We do this by partnering to deliver turnkey products and services that are simple to implement and administer; customizable to meet the unique...
Chubb
Bärengasse 32, CH-8001, CH
Last Update: 05/07/2026
Chubb is a world leader in insurance. With operations in 54 countries and territories, Chubb provides commercial and personal property and casualty insurance, personal accident and supplemental health insurance, reinsurance and life insurance to a diverse group of clien...
Compliance Ranges Comparison
Amplifon Hearing Health Care
Chubb
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Amplifon Hearing Health Care in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Chubb in 2026.
Incident History - Amplifon Hearing Health Care (X = Date, Y = Severity)
Amplifon Hearing Health Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Chubb (X = Date, Y = Severity)
Chubb cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Amplifon Hearing Health Care
Chubb
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: *.*.