Comparison Overview
Sherman Oaks Hospital
Sherman Oaks Hospital
4929 Van Nuys Blvd, Sherman Oaks, 91403, US
Last Update: 04/04/2026
We are committed to making our facility a safe place for care. You can rest assured that we’ve taken all the steps we can to protect you and those you love. Sherman Oaks Hospital is making sure you don’t have to choose between safety and getting the care you need in the...
Hapvida NotreDame Intermédica
Av. Paulista 867, São Paulo, 01311-100, BR
Last Update: 02/04/2026
Com cerca de 80 anos de experiência, a Hapvida é hoje a maior empresa de saúde integrada da América Latina. A companhia, que possui mais de 69 mil colaboradores, atende quase 16 milhões de beneficiários de saúde e odontologia espalhados pelas cinco regiões do Brasil. T...
Compliance Ranges Comparison
Sherman Oaks Hospital
Hapvida NotreDame Intermédica
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sherman Oaks Hospital in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Hapvida NotreDame Intermédica in 2026.
Incident History - Sherman Oaks Hospital (X = Date, Y = Severity)
Sherman Oaks Hospital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapvida NotreDame Intermédica (X = Date, Y = Severity)
Hapvida NotreDame Intermédica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sherman Oaks Hospital
Hapvida NotreDame Intermédica
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: *.*.