Comparison Overview
McKinsey Tech, Media and Telecom
McKinsey Tech, Media and Telecom
N/A
Last Update: 05/12/2025
Technology, media, and telecommunications companies are at the heart of the digital economy—building the infrastructure and devices that connect people, businesses, and countries. Companies across these industries generate more economic profit than any other sector of t...
BearingPoint
BearingPoint B.V., Amsterdam, NL-1101 BH, NL
Last Update: 05/04/2026
BearingPoint is an independent management and technology consultancy. Our roots are European, but our footprint is truly global. Transformation is our core service. We deliver value to enterprises, government organizations and NGOs. In a rapidly changing world, Bearing...
Compliance Ranges Comparison
McKinsey Tech, Media and Telecom
BearingPoint
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for McKinsey Tech, Media and Telecom in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for BearingPoint in 2026.
Incident History - McKinsey Tech, Media and Telecom (X = Date, Y = Severity)
McKinsey Tech, Media and Telecom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BearingPoint (X = Date, Y = Severity)
BearingPoint cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
McKinsey Tech, Media and Telecom
BearingPoint
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: *.*.