Comparison Overview
Young & Rubicam
Young & Rubicam
3 Columbus Circle, New York, NY, 10019, US
Last Update: 30/12/2025
Y&R is a leading global marketing communications company, with more than 189 offices in 90+ countries. Our job is to Resist the Usual – the mission Y&R was founded on in 1923. We operate as a global boutique; our agencies have the authenticity of their local markets a...
Clear Channel Europe
33 Golden Square, London, England, GB, W1F 9
Last Update: 01/04/2026
Clear Channel Europe is a division of leading global Out of Home media company, Clear Channel Outdoor Holdings, Inc. (NYSE: CCO). The Clear Channel Europe portfolio spans 14 markets with 260,000 advertising panels. Clear Channel Europe has 2,600 dedicated employees. O...
Compliance Ranges Comparison
Young & Rubicam
Clear Channel Europe
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Young & Rubicam in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Clear Channel Europe in 2026.
Incident History - Young & Rubicam (X = Date, Y = Severity)
Young & Rubicam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Clear Channel Europe (X = Date, Y = Severity)
Clear Channel Europe cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Young & Rubicam
Clear Channel Europe
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: *.*.