Comparison Overview
RBC Dominion Securities
RBC Dominion Securities
155 Wellington Street West, Toronto, M5V 3K7, CA
Last Update: 01/02/2026
At RBC Dominion Securities, our vision is simple: to always earn the right to be our clients’ first choice for wealth management services. We know that to achieve this vision, we must invest in our business and ensure our advisors have access to best-in-class tools and ...
Sonae
Maia, Porto, 4470-177, PT
Last Update: 04/04/2026
Sonae exists to create a lasting positive impact on businesses, people, communities and on the planet. Managing a diverse portfolio of businesses in retail, financial services, technology, investments, real estate and telecommunications, Sonae makes the most of its ex...
Compliance Ranges Comparison
RBC Dominion Securities
Sonae
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for RBC Dominion Securities in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Sonae in 2026.
Incident History - RBC Dominion Securities (X = Date, Y = Severity)
RBC Dominion Securities cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sonae (X = Date, Y = Severity)
Sonae cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
RBC Dominion Securities
Sonae
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: *.*.