Comparison Overview
Marcus by Goldman Sachs
Marcus by Goldman Sachs
N/A
Last Update: 01/03/2026
At Marcus by Goldman Sachs, we know it’s about more than just money. It’s about getting your money to keep pace with your ambitions. Learn how our suite of financial products like high-yield online savings and lending helps you do just that. And discover how we can leve...
Revolut
30 S Colonnade, London, E14 5HX, GB
Last Update: 22/04/2026
People deserve more from their money. More visibility, more control, and more freedom. Since 2015, Revolut has been on a mission to deliver just that. Our powerhouse of products help our 65+ million customers get more from their money every day. As we continue our ligh...
Compliance Ranges Comparison
Marcus by Goldman Sachs
Revolut
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Marcus by Goldman Sachs in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Revolut in 2026.
Incident History - Marcus by Goldman Sachs (X = Date, Y = Severity)
Marcus by Goldman Sachs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Revolut (X = Date, Y = Severity)
Revolut cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Marcus by Goldman Sachs
Revolut
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: *.*.