Comparison Overview
VNA An Affiliate of Midland Care Connection

VNA An Affiliate of Midland Care Connection
1300 E 104th St, Kansas City, 64131, US
Last Update: 03/04/2026
Established in 1891, Visiting Nurse Association (VNA) is Kansas City’s first home health agency and home to the original visiting nurse, Lilly Major. “The visiting nurse brought her skill and compassion to all Kansas City neighborhoods…” and thus began the tradition of...

EsSalud
120 Jirón Domingo Cueto, Jesús María, 15072, PE
Last Update: 31/03/2026
El Seguro Social de Salud, EsSalud, es un organismo público descentralizado, con personería jurídica de derecho público interno, adscrito al Sector Trabajo y Promoción Social. Tiene por finalidad dar cobertura a los asegurados y sus derechohabientes, a través del otorg...
Compliance Ranges Comparison

VNA An Affiliate of Midland Care Connection







EsSalud






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for VNA An Affiliate of Midland Care Connection in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for EsSalud in 2026.
Incident History - VNA An Affiliate of Midland Care Connection (X = Date, Y = Severity)
VNA An Affiliate of Midland Care Connection cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EsSalud (X = Date, Y = Severity)
EsSalud cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

VNA An Affiliate of Midland Care Connection

EsSalud
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: *.*.