Comparison Overview
MoneyGram
MoneyGram
2828 N. Harwood,15th Floor, Dallas, 75201, US
Last Update: 04/04/2026
MoneyGram connects the world by making the movement of money across borders seamless, affordable and secure for everyone. Each year, the company serves more than 50 million people in over 200 countries and territories. Headquartered in Dallas, Texas, with offices in 3...
Scalable Capital
Seitzstraße 8e, München, 80538, DE
Last Update: 31/03/2026
Scalable Capital is a leading digital banking and investment platform with a full banking licence, enabling people in Europe to take control of their finances. The company was founded in 2014 and has offices in Munich, Berlin, Vienna, Milan and London. For private ind...
Compliance Ranges Comparison
MoneyGram
Scalable Capital
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for MoneyGram in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Scalable Capital in 2026.
Incident History - MoneyGram (X = Date, Y = Severity)
MoneyGram cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Scalable Capital (X = Date, Y = Severity)
Scalable Capital cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MoneyGram
Scalable Capital
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: *.*.