Comparison Overview
HCA Florida Gulf Coast Hospital
HCA Florida Gulf Coast Hospital
449 W 23rd St, Panama City, 32405, US
Last Update: 03/04/2026
Gulf Coast Regional Medical Center is now HCA Florida Gulf Coast Hospital. As a fully accredited, 223-bed facility, we offer comprehensive care in Panama City, including advanced cardiac assessment and treatment, certified women's services and dedicated spaces for adult...
NMC Healthcare
Al Ain Towers, Al Khalidiyah St - Al Bateen - W10, Abu Dhabi, AE
Last Update: 02/04/2026
NMC Healthcare is one of the largest private healthcare networks in the United Arab Emirates. Since 1975, we have provided high quality, personalised, and compassionate care to our patients and are proud to have earned the trust of millions of people in the UAE and arou...
Compliance Ranges Comparison
HCA Florida Gulf Coast Hospital
NMC Healthcare
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for HCA Florida Gulf Coast Hospital in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for NMC Healthcare in 2026.
Incident History - HCA Florida Gulf Coast Hospital (X = Date, Y = Severity)
HCA Florida Gulf Coast Hospital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NMC Healthcare (X = Date, Y = Severity)
NMC Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HCA Florida Gulf Coast Hospital
NMC Healthcare
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: *.*.