Comparison Overview
Longview Regional Medical Center
Longview Regional Medical Center
2901 N. Fourth Street , Longview, TX, 75605, undefined
Last Update: 05/05/2026
Serving the East Texas region with trusted, quality care. Healing begins here. Longview Regional Medical Center is your community healthcare provider; a 230-bed facility. We believe in the power of people to create great care. We're 180 physicians and healthcare profe...
Erasmus MC
Dr. Molewaterplein 40, Rotterdam, Zuid-Holland, NL, 3015 GD
Last Update: 03/04/2026
We are Erasmus MC. Our roots lie in Rotterdam, a city and port of international standing. We are the most innovative university medical center in the Netherlands and one of the world’s leading centers of scientific research. We are committed to achieving a healthy popul...
Compliance Ranges Comparison
Longview Regional Medical Center
Erasmus MC
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Longview Regional Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Erasmus MC in 2026.
Incident History - Longview Regional Medical Center (X = Date, Y = Severity)
Longview Regional Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Erasmus MC (X = Date, Y = Severity)
Erasmus MC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Longview Regional Medical Center
Erasmus MC
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: *.*.