Comparison Overview
Johns Hopkins Kimmel Cancer Center
Johns Hopkins Kimmel Cancer Center
Baltimore, US
Last Update: 09/03/2026
Since its opening in 1973, our Cancer Center has led the world in deciphering the mechanisms of cancer and new ways to treat it. The strength of our research and treatment programs was recognized early on by the National Cancer Institute, becoming one of the first to e...
Amsterdam UMC
Meibergdreef 9, Amsterdam, 1100 DE, NL
Last Update: 01/04/2026
At Amsterdam UMC, more than 15,000 professionals strive to provide good and accessible care. For the generations of today and tomorrow. The two medical university centers in Amsterdam, AMC and VUmc, are working together towards a future in which we prevent illnesses and...
Compliance Ranges Comparison
Johns Hopkins Kimmel Cancer Center
Amsterdam UMC
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Johns Hopkins Kimmel Cancer Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Amsterdam UMC in 2026.
Incident History - Johns Hopkins Kimmel Cancer Center (X = Date, Y = Severity)
Johns Hopkins Kimmel Cancer Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amsterdam UMC (X = Date, Y = Severity)
Amsterdam UMC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Johns Hopkins Kimmel Cancer Center
Amsterdam UMC
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: *.*.