Comparison Overview
Pro Medicus Limited
Pro Medicus Limited
450 Swan St, Richmond VIC, 3121, AU
Last Update: 31/03/2026
Pro Medicus Limited [ASX: PME] is a leading imaging IT provider. Founded in 1983, the company provides a full range of radiology IT software and services to hospitals, imaging centres and health care groups worldwide. In late January 2009, the company announced the purc...
Inova Health
3300 Gallows Road, Falls Church, Virginia, US, 22042
Last Update: 01/04/2026
We are Inova, Northern Virginia and the Washington, D.C. metropolitan area’s leading nonprofit healthcare provider. With expertise and compassion, we partner with our patients to help them stay healthy. We treat illness, heal injury and look at a patient’s whole health ...
Compliance Ranges Comparison
Pro Medicus Limited
Inova Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Pro Medicus Limited in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Inova Health in 2026.
Incident History - Pro Medicus Limited (X = Date, Y = Severity)
Pro Medicus Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Inova Health (X = Date, Y = Severity)
Inova Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pro Medicus Limited
Inova Health
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: *.*.