Comparison Overview
Harbor Health Services, Inc.
Harbor Health Services, Inc.
1135 Morton Street, Mattapan, 02126, US
Last Update: 01/04/2026
Harbor Health Services, Inc. is a nonprofit, public health agency committed to providing quality, comprehensive health care in Metropolitan Boston urban neighborhoods, the South Shore and Cape Cod communities. We provide a wide network of health care services. Harbor ...
Keralty
Calle 100 # 11b -67, Bogota, 110111, CO
Last Update: 30/03/2026
Anteriormente Organización Sanitas Internacional, Keralty es un grupo empresarial de valor en salud, con más de 40 años de experiencia conformado por empresas de aseguramiento y prestación de servicios de salud y una red propia hospitalaria y asistencial. También form...
Compliance Ranges Comparison
Harbor Health Services, Inc.
Keralty
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Harbor Health Services, Inc. in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Keralty in 2026.
Incident History - Harbor Health Services, Inc. (X = Date, Y = Severity)
Harbor Health Services, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Keralty (X = Date, Y = Severity)
Keralty cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Harbor Health Services, Inc.
Keralty
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: *.*.