Comparison Overview
KU Leuven ICTS
KU Leuven ICTS
Willem de Croylaan 52, Heverlee, Vlaams-Brabant, 3001, BE
Last Update: 14/02/2026
ICTS is the central computer department of KU Leuven. ICTS manages the central IT infrastructure, central databases, all servers (from mail servers to web servers) and the High Performance Cluster for scientific computing.
Neobpo
Rua Pais Leme, 14, São Paulo, SP, BR, 05424-010
Last Update: 03/04/2026
Somos especializados em integrar tecnologia com inteligência humana, oferecendo soluções digitais que promovem transformação e eficiência operacional. Nosso foco é gerar valor por meio de resultados reais, utilizando inteligência digital para atender às necessidades esp...
Compliance Ranges Comparison
KU Leuven ICTS
Neobpo
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for KU Leuven ICTS in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Neobpo in 2026.
Incident History - KU Leuven ICTS (X = Date, Y = Severity)
KU Leuven ICTS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Neobpo (X = Date, Y = Severity)
Neobpo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
KU Leuven ICTS
Neobpo
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: *.*.