Comparison Overview
Institute for Security Science and Technology (ISST), Imperial College London
Institute for Security Science and Technology (ISST), Imperial College London
Imperial College London, London, SW7 2AZ, GB
Last Update: 25/12/2025
The ISST was founded in 2008 as one of Imperial College's Global Challenge Institutes. We seek to improve security and resilience across a range of scales, from the individual to whole populations.
Technical University of Munich
Arcisstraße 21, München, Munich, Bavaria, DE, 80333
Last Update: 02/04/2026
Our university combines top-class facilities for cutting-edge research with unique learning opportunities for 52,000 students. Whether our researchers are investigating the origins of life, matter and the universe or looking for solutions to the major challenges for our...
Compliance Ranges Comparison
Institute for Security Science and Technology (ISST), Imperial College London
Technical University of Munich
Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Institute for Security Science and Technology (ISST), Imperial College London in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Technical University of Munich in 2026.
Incident History - Institute for Security Science and Technology (ISST), Imperial College London (X = Date, Y = Severity)
Institute for Security Science and Technology (ISST), Imperial College London cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Technical University of Munich (X = Date, Y = Severity)
Technical University of Munich cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Institute for Security Science and Technology (ISST), Imperial College London
Technical University of Munich
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: *.*.