Comparison Overview

Chase

VS

Wells Fargo

Chase

270 Park Avenue, New York, 10172, US
Last Update: 2026-01-17
Between 750 and 799

At Chase, we’re dedicated to helping you succeed. Whether you’re in need of banking, credit cards, mortgages, auto financing, investment guidance, small business support, or payment solutions, we’re beside you every step of the way. For customer service, contact us via chase.com/customerservice. See full social media terms and conditions at chase.com/socialterms. JPMorgan Chase is an Equal Opportunity Employer, including Disability/Veterans.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 34,537
Subsidiaries: 11
12-month incidents
0
Known data breaches
10
Attack type number
3

Wells Fargo

420 Montgomery St, San Francisco, California, US, 94103
Last Update: 2026-01-17
Between 800 and 849

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 headquartered in San Francisco, Wells Fargo provides banking, investment and mortgage products and services, as well as consumer and commercial finance, through more than 7,300 locations, 12,000 ATMs, the internet (wellsfargo.com) and mobile banking, and has offices in over 40 countries and territories to support customers who conduct business in the global economy. With approximately 250,000 team members, Wells Fargo serves one in three households in the United States. Wells Fargo & Company was ranked No. 41 on Fortune’s 2022 rankings of America’s largest corporations. News, insights and perspectives from Wells Fargo are also available at Wells Fargo Stories. Relevant military experience is considered for veterans and transitioning service men and women. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, status as a protected veteran, or any other legally protected characteristic.© 2016 Wells Fargo Bank, N.A. All rights reserved. Member FDIC.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 221,512
Subsidiaries: 2
12-month incidents
0
Known data breaches
4
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/chase.jpeg
Chase
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/wellsfargo.jpeg
Wells Fargo
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Chase
100%
Compliance Rate
0/4 Standards Verified
Wells Fargo
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Chase in 2026.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Wells Fargo in 2026.

Incident History — Chase (X = Date, Y = Severity)

Chase cyber incidents detection timeline including parent company and subsidiaries

Incident History — Wells Fargo (X = Date, Y = Severity)

Wells Fargo cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/chase.jpeg
Chase
Incidents

Date Detected: 11/2025
Type:Breach
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Compromised User Account
Blog: Blog

Date Detected: 5/2025
Type:Ransomware
Attack Vector: Legitimate software and open-source pen-testing tools
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/wellsfargo.jpeg
Wells Fargo
Incidents

Date Detected: 5/2022
Type:Breach
Attack Vector: Unauthorized Access (Insider)
Blog: Blog

Date Detected: 12/2021
Type:Breach
Attack Vector: Email
Blog: Blog

Date Detected: 11/2019
Type:Breach
Attack Vector: Human Error (Email Misdelivery)
Blog: Blog

FAQ

Wells Fargo company demonstrates a stronger AI Cybersecurity Score compared to Chase company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Chase company has faced a higher number of disclosed cyber incidents historically compared to Wells Fargo company.

In the current year, Wells Fargo company and Chase company have not reported any cyber incidents.

Chase company has confirmed experiencing a ransomware attack, while Wells Fargo company has not reported such incidents publicly.

Both Wells Fargo company and Chase company have disclosed experiencing at least one data breach.

Neither Wells Fargo company nor Chase company has reported experiencing targeted cyberattacks publicly.

Chase company has disclosed at least one vulnerability, while Wells Fargo company has not reported such incidents publicly.

Neither Chase nor Wells Fargo holds any compliance certifications.

Neither company holds any compliance certifications.

Chase company has more subsidiaries worldwide compared to Wells Fargo company.

Wells Fargo company employs more people globally than Chase company, reflecting its scale as a Financial Services.

Neither Chase nor Wells Fargo holds SOC 2 Type 1 certification.

Neither Chase nor Wells Fargo holds SOC 2 Type 2 certification.

Neither Chase nor Wells Fargo holds ISO 27001 certification.

Neither Chase nor Wells Fargo holds PCI DSS certification.

Neither Chase nor Wells Fargo holds HIPAA certification.

Neither Chase nor Wells Fargo holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H