Comparison Overview
Wells Fargo
Wells Fargo
420 Montgomery St, San Francisco, California, US, 94103
Last Update: 07/09/2026
Wells Fargo & Company (NYSE: WFC) is a diversified, community-based financial services company with approximately $1.9 trillion in assets. Wells Fargo’s vision is to satisfy our customers’ financial needs and help them succeed financially. Founded in 1852 and headquarte...
Santander US
75 State Street, Boston, 02109, US
Last Update: 12/09/2026
Santander’s purpose is to help people and businesses prosper. In the United States, Santander is a leading financial services provider with approximately 11,000 employees, 4.3 million customers, and assets of $243 billion, as of Q4 2025. Our five diverse and growing bu...
Compliance Ranges Comparison
Wells Fargo
Santander US
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Wells Fargo in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Santander US in 2026.
Incident History - Wells Fargo (X = Date, Y = Severity)
Wells Fargo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Santander US (X = Date, Y = Severity)
Santander US cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wells Fargo
Santander US
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout