Comparison Overview
J.P. Morgan Commercial and Investment Banking
J.P. Morgan Commercial and Investment Banking
New York, New York, US, 0
Last Update: 01/04/2026
J.P. Morgan's Commercial, Corporate and Investment Banking businesses provide a complete set of solutions and capabilities to our clients around the world. We’re committed to supporting our clients through every stage in their life cycle, from emerging startups to large...
Equifax
P.O. Box 740241, Atlanta, 30374, US
Last Update: 13/09/2026
At Equifax (NYSE: EFX), we believe knowledge drives progress. As a global data, analytics, and technology company, we play an essential role in the global economy by helping financial institutions, companies, employers, and government agencies make critical decisions wi...
Compliance Ranges Comparison
J.P. Morgan Commercial and Investment Banking
Equifax
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for J.P. Morgan Commercial and Investment Banking in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Equifax has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - J.P. Morgan Commercial and Investment Banking (X = Date, Y = Severity)
J.P. Morgan Commercial and Investment Banking cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Equifax (X = Date, Y = Severity)
Equifax cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
J.P. Morgan Commercial and Investment Banking
Equifax
FAQ
Latest Global CVEs
A malicious user can get read-access to files in the flatpak-system-helper context if a system OCI repository is configured, because the OCI code paths in the system helper follow symlinks when importing OCI images that are under the user's control.
A vulnerability was identified in Seetong T8108, T8108P, T8116 and T8232 4.6.1.4-build202604241011. The affected element is an unknown function of the component Debug Service. Such manipulation leads to improper authentication. The attack may be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Krayin laravel-crm up to 2.2.4. This affects an unknown function of the file packages/Webkul/Installer/src/Http/Middleware/CanInstall.php of the component admin-config-setup API Endpoint. The manipulation results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used. Upgrading to version 2.2.5 mitigates this issue. The patch is identified as 89f2916b6a46ff91bd1999ce38158fa0de8b9490. Upgrading the affected component is recommended.
- https://github.com/carlosalbertotuma/advisory/blob/main/advisory-07-Unauthenticated-InstallerBypass.md
- https://github.com/krayin/laravel-crm/
- https://github.com/krayin/laravel-crm/commit/89f2916b6a46ff91bd1999ce38158fa0de8b9490
- https://github.com/krayin/laravel-crm/pull/2614
- https://github.com/krayin/laravel-crm/releases/tag/v2.2.5
- https://vuldb.com/cve/CVE-2026-100885
- https://vuldb.com/submit/916597
- https://vuldb.com/vuln/410815
- https://vuldb.com/vuln/410815/cti
A vulnerability has been found in Krayin laravel-crm up to 2.2.5. The impacted element is the function Storage::download of the file packages/Webkul/Admin/src/Config/acl.php of the component attachment-download Endpoint. The manipulation of the argument ID leads to improper control of resource identifiers. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.2.6 is sufficient to resolve this issue. The identifier of the patch is 13d6988cda8d69ece45ee1890effc90a7f21cdc1. It is suggested to upgrade the affected component.
- https://github.com/carlosalbertotuma/advisory/blob/main/advisory-06-IDOR-Email-Attachment%20Download.md
- https://github.com/krayin/laravel-crm/
- https://github.com/krayin/laravel-crm/commit/13d6988cda8d69ece45ee1890effc90a7f21cdc1
- https://github.com/krayin/laravel-crm/issues/2624
- https://github.com/krayin/laravel-crm/pull/2627
- https://github.com/krayin/laravel-crm/releases/tag/v2.2.6
- https://vuldb.com/cve/CVE-2026-100884
- https://vuldb.com/submit/916218
- https://vuldb.com/vuln/410814
- https://vuldb.com/vuln/410814/cti
A flaw has been found in Krayin laravel-crm up to 2.2.5. The affected element is an unknown function of the file packages/Webkul/Admin/src/Config/acl.php. Executing a manipulation can lead to improper access controls. The attack can be launched remotely. The exploit has been published and may be used. Upgrading to version 2.2.6 is sufficient to fix this issue. This patch is called a399404a388d8ad2700a01349d0d98069c8e85a4. The affected component should be upgraded.
- https://github.com/carlosalbertotuma/advisory/blob/main/advisory-05-Missing-Function-Level%20Authorization.md
- https://github.com/krayin/laravel-crm/
- https://github.com/krayin/laravel-crm/commit/a399404a388d8ad2700a01349d0d98069c8e85a4
- https://github.com/krayin/laravel-crm/issues/2623
- https://github.com/krayin/laravel-crm/pull/2626
- https://github.com/krayin/laravel-crm/releases/tag/v2.2.6
- https://vuldb.com/cve/CVE-2026-100883
- https://vuldb.com/submit/916128
- https://vuldb.com/vuln/410813
- https://vuldb.com/vuln/410813/cti