Comparison Overview
UNC Health
UNC Health
101 Manning Drive, Chapel Hill, North Carolina, US, 27516
Last Update: 01/04/2026
Our mission is to improve the health and well-being of North Carolinians and others whom we serve. We accomplish this by providing leadership and excellence in the interrelated areas of patient care, education and research. UNC Health and its 40,000 teammates, continue...
Bon Secours
1505 Marriottsville Road, Marriottsville, 21104, US
Last Update: 02/04/2026
Bon Secours Health System, Inc. based in Marriottsville, Maryland, is a $3.2 billion dollar not-for-profit Catholic health system that owns, manages or joint ventures 18 acute care, 5 long term care, 4 assisted living, 6 retirement communities/senior housing, 14 home ca...
Compliance Ranges Comparison
UNC Health
Bon Secours
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UNC Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Bon Secours in 2026.
Incident History - UNC Health (X = Date, Y = Severity)
UNC Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bon Secours (X = Date, Y = Severity)
Bon Secours cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UNC Health
Bon Secours
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: *.*.