Comparison Overview
Lumexa Imaging
Lumexa Imaging
4200 Six Forks Road, Raleigh, 27609, US
Last Update: 08/07/2026
Lumexa Imaging is one of the nation’s largest providers of outpatient medical imaging, with a mission to expand access to advanced, high-quality, and affordable diagnostic care. We operate more than 180 centers across 13 states, including more than 85 centers in joint v...
Region Hovedstaden
Kongens Vaenge 2, Hillerod, 3400, DK
Last Update: 04/04/2026
Det handler om liv. Om at bringe liv til verden og skabe livskvalitet. Om at redde liv og forbedre liv. Som medarbejder i Region Hovedstaden træder du ind i en verden af muligheder og mangfoldighed med plads til dine ambitioner. Du er en del af et stærkt fagligt miljø, ...
Compliance Ranges Comparison
Lumexa Imaging
Region Hovedstaden
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Lumexa Imaging has 40.85% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Region Hovedstaden in 2026.
Incident History - Lumexa Imaging (X = Date, Y = Severity)
Lumexa Imaging cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Region Hovedstaden (X = Date, Y = Severity)
Region Hovedstaden cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Lumexa Imaging
Region Hovedstaden
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: *.*.