Comparison Overview
Santander Consumer USA

Santander Consumer USA
1601 Elm St, Dallas, 75201, US
Last Update: 23/03/2026
In 1995, a group of young entrepreneurs thought they could make their mark on the world of automotive finance by thinking a little bigger and a lot bolder than the competition. It turns out, they were right. The explosive growth and success of the new company quickly ca...

Goldman Sachs
200 West Street, New York, 10282, US
Last Update: 20/05/2026
We aspire to be the world’s most exceptional financial institution, united by our shared values of partnership, client service, integrity, and excellence. Operating at the center of capital markets, we act as one firm, mobilizing our people, capital, and ideas to deli...
Compliance Ranges Comparison

Santander Consumer USA







Goldman Sachs






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Santander Consumer USA in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Goldman Sachs has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Santander Consumer USA (X = Date, Y = Severity)
Santander Consumer USA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Goldman Sachs (X = Date, Y = Severity)
Goldman Sachs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Santander Consumer USA

Goldman Sachs
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.