Comparison Overview
Radio France
Radio France
116 Avenue du Président Kennedy, PARIS Cedex 16, undefined, 75220, FR
Last Update: 16/05/2026
Née en 1975 de l’éclatement de l’établissement public ORTF, Radio France est une société nationale de radiodiffusion, constituée sous la forme d’une société anonyme à capitaux publics dont l’Etat est l’unique l’actionnaire. Premier groupe radiophonique français, Radi...
CBC/Radio-Canada
181 Queen Street, Ottawa, K1Y 1E4, CA
Last Update: 01/04/2026
CBC/Radio-Canada is Canada's national public broadcaster and a strong advocate of Canadian culture. We offer a unique space and a fresh Canadian perspective with unmatched cultural, musical and documentary programming. We do it in French, English and eight Aboriginal l...
Compliance Ranges Comparison
Radio France
CBC/Radio-Canada
Benchmark & Cyber Underwriting Signals
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for Radio France in 2026.
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for CBC/Radio-Canada in 2026.
Incident History - Radio France (X = Date, Y = Severity)
Radio France cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CBC/Radio-Canada (X = Date, Y = Severity)
CBC/Radio-Canada cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Radio France
CBC/Radio-Canada
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: *.*.