Comparison Overview
SmileDentalCenter
SmileDentalCenter
Toronto, ON M6N 1J4, CA
Last Update: 01/04/2026
The mission at Smile Dental Centre is to provide an astonishing experience for our patients and provide them with the treatment they need at an affordable price. Our team is highly skilled and is experienced in handling all aspects of dentistry, no matter the complexity...
WellSpan Health
45 Monument Road, York, 17403, US
Last Update: 03/04/2026
WellSpan Health’s vision is to reimagine healthcare through the delivery of comprehensive, equitable health and wellness solutions throughout our continuum of care. As an integrated delivery system focused on leading in value-based care, we encompass more than 2,500 emp...
Compliance Ranges Comparison
SmileDentalCenter
WellSpan Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for SmileDentalCenter in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for WellSpan Health in 2026.
Incident History - SmileDentalCenter (X = Date, Y = Severity)
SmileDentalCenter cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WellSpan Health (X = Date, Y = Severity)
WellSpan Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SmileDentalCenter
WellSpan Health
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: *.*.