Comparison Overview
Université Paris Cité
Université Paris Cité
12 rue de l’École de Médecine, None, Paris, Ile de France, FR, 75006
Last Update: 16/03/2026
This university of intensive research embodies the incarnation of a Modern Paris. It contributes to a higher education, research and innovation in France, but also to the European and International dimension of research and formation. Université de Paris based on the s...
University of Colorado Boulder
914 Broadway St, Boulder, Colorado, US
Last Update: 02/04/2026
The University of Colorado Boulder is Colorado’s leading public research university, transforming lives since 1876. As the state's flagship university and one of only 38 U.S. public research institutions in the Association of American Universities (AAU), CU Boulder has...
Compliance Ranges Comparison
Université Paris Cité
University of Colorado Boulder
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Université Paris Cité in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Colorado Boulder in 2026.
Incident History - Université Paris Cité (X = Date, Y = Severity)
Université Paris Cité cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Colorado Boulder (X = Date, Y = Severity)
University of Colorado Boulder cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Université Paris Cité
University of Colorado Boulder
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: *.*.