Comparison Overview
Signia Hearing
Signia Hearing
18 Tai Seng Street, Singapore , Singapore , 91052, SG
Last Update: 22/03/2026
Signia is one of the leading hearing aid brands in the world. Our goal is to enhance human performance through iconic innovations that shape the prescription audio category. We refuse to accept hearing loss as a limitation. With Signia, you can be brilliant.
Dentsply Sirona
13320 Ballantyne Corporate Pl, Charlotte, North Carolina, US, 28277
Last Update: 02/04/2026
A Global Total Solutions Provider Dentsply Sirona is the world’s largest manufacturer of professional dental products and technologies, empowering dental professionals to provide better, safer and faster dental care. Our products and solutions include leading position...
Compliance Ranges Comparison
Signia Hearing
Dentsply Sirona
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Device Industry Avg (This Year)
No incidents recorded for Signia Hearing in 2026.
Incidents vs Medical Device Industry Avg (This Year)
No incidents recorded for Dentsply Sirona in 2026.
Incident History - Signia Hearing (X = Date, Y = Severity)
Signia Hearing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dentsply Sirona (X = Date, Y = Severity)
Dentsply Sirona cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Signia Hearing
Dentsply Sirona
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: *.*.