Comparison Overview
Smila
Smila
Rajatorpantie 41 B, Vantaa, FI, 01640
Last Update: 31/10/2025
Focusing on good life at home and in nursing homes Smila is user-friendly and designed for home use or at a care unit, ensuring safe, up-to-date and effective medication and enabling independent everyday life at home.
UCSF Health
505 Parnassus Avenue, San Francisco, 94143, US
Last Update: 30/03/2026
UCSF Health is an integrated health care network encompassing several entities, including UCSF Medical Center, one of the nation’s top 10 hospitals according to U.S. News & World Report, and UCSF Benioff Children’s Hospitals, with campuses in Oakland and San Francisco. ...
Compliance Ranges Comparison
Smila
UCSF Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Smila in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UCSF Health in 2026.
Incident History - Smila (X = Date, Y = Severity)
Smila cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UCSF Health (X = Date, Y = Severity)
UCSF Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Smila
UCSF 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: *.*.