Comparison Overview
Beltone New England
Beltone New England
931 Jefferson Blvd Suite 2001, Warwick, RI 02886, US
Last Update: 25/02/2026
Welcome to the Beltone New England Hearing Aid Center. We are one of the largest privately owned Reatil Hearing Aid practices in the USA. Michael Andreozzi started Beltone New England in 2002 with 7 retail locations in Rhode Island and has grown it over 100 locations i...
Alcon
Avenue Louis-Casaï 58, Geneva, Switzerland, CH, 1216
Last Update: 09/07/2026
Alcon helps people see brilliantly. As the global leader in eye care with a heritage spanning over 75 years, we offer the broadest portfolio of products to enhance sight and improve people’s lives. Our Surgical and Vision Care products touch the lives of more than 260 m...
Compliance Ranges Comparison
Beltone New England
Alcon
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Beltone New England in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Alcon has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Beltone New England (X = Date, Y = Severity)
Beltone New England cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alcon (X = Date, Y = Severity)
Alcon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Beltone New England
Alcon
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: *.*.