Comparison Overview
Sykehuset Innlandet
Sykehuset Innlandet
Furnesveien 26, Brumunddal, Brumunddal, 2381, NO
Last Update: 26/01/2026
Sykehuset Innlandet HF er et av landets største helseforetak med om lag 10 000 ansatte, og et stort antall faggrupper. Helseforetaket har virksomhet på 49 ulike steder i Hedmark og Oppland innen somatikk, psykisk helsevern, rusomsorg og prehospitale tjenester. Sykehuset...
Lehigh Valley Health Network
1200 S Cedar Crest Blvd, Allentown, Pennsylvania, US, 18103
Last Update: 03/04/2026
Lehigh Valley Health Network, part of Jefferson Health, is proud to be part of a leading integrated academic health care delivery system. Together, we’re among the top 15 not-for-profit health systems in the U.S., with 65,000 colleagues, 32 hospitals and more than 700 ...
Compliance Ranges Comparison
Sykehuset Innlandet
Lehigh Valley Health Network
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sykehuset Innlandet in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Lehigh Valley Health Network in 2026.
Incident History - Sykehuset Innlandet (X = Date, Y = Severity)
Sykehuset Innlandet cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lehigh Valley Health Network (X = Date, Y = Severity)
Lehigh Valley Health Network cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sykehuset Innlandet
Lehigh Valley Health Network
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: *.*.