Comparison Overview
National Bank of Canada

National Bank of Canada
800 Rue Saint-Jacques, Montreal, Quebec, CA, H3C 1A3
Last Update: 15/09/2026
At National Bank, we believe in the potential of each individual, and that even the smallest gestures can make a big difference. When we help others accomplish their projects, we help empower them and the community at large. We try to make a difference through innova...

CIC
6, Avenue de Provence, Paris, Île-de-France, FR, 75009
Last Update: 01/04/2026
CIC is the fourth largest banking group in France, consisting of seven regional banks which operate across France through a network of 1,844 branches employing 24,000 staff. CIC's customer base includes 2.7 million retail clients. One in eleven self-employed professiona...
Compliance Ranges Comparison

National Bank of Canada







CIC






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for National Bank of Canada in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for CIC in 2026.
Incident History - National Bank of Canada (X = Date, Y = Severity)
National Bank of Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CIC (X = Date, Y = Severity)
CIC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

National Bank of Canada

CIC
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.