Comparison Overview
FAPE EDF
FAPE EDF
4, Rue Floréal, Paris, 75017, FR
Last Update: 24/02/2026
Géré collégialement par les entreprises du groupe EDF et les organisations syndicales, le Fonds Agir Pour l’Emploi du groupe EDF est financé en premier lieu par les dons des salariés et retraités du Groupe. Le FAPE groupe EDF accompagne et finance des projets concrets ...
Transport for London
5 Endeavour Square, Westfield Avenue,, London , E20 1JN, GB
Last Update: 04/04/2026
Every day, we help millions of people to make journeys across London: By Tube, bus, tram, car, bike – and more. People don’t associate us with journeys by river, on foot or via the air, but we help with that, too. Getting people to where they need to go has been our bus...
Compliance Ranges Comparison
FAPE EDF
Transport for London
Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for FAPE EDF in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Transport for London in 2026.
Incident History - FAPE EDF (X = Date, Y = Severity)
FAPE EDF cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Transport for London (X = Date, Y = Severity)
Transport for London cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
FAPE EDF
Transport for London
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: *.*.