Comparison Overview
Banco Pichincha Perú

Banco Pichincha Perú
AV. RICARDO PALMA 278, Lima, Lima, LI18, PE
Last Update: 07/03/2026
La historia de nuestro Banco se inicia en Julio de 1964, como Financiera y Promotora de la Construcción S.A. Luego en enero de 1982, se modificó su denominación a FINANPRO Empresa Financiera. Es el 21 de Noviembre de 1986 cuando nos constituimos como el Banco comercial ...

National Bank of Canada
800 Rue Saint-Jacques, Montreal, Quebec, CA, H3C 1A3
Last Update: 05/04/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...
Compliance Ranges Comparison

Banco Pichincha Perú







National Bank of Canada






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

Banco Pichincha Perú

National Bank of Canada
FAQ
Latest Global CVEs
An OS command injection vulnerability exists in the VPN module of TP-Link AXE75 V1 routers. This vulnerability allows an adjacent, authenticated attacker to execute arbitrary commands on the device by importing a specially crafted VPN client configuration file. The issue arises from improper filtering of special characters. Successful exploitation of this vulnerability may enable an attacker to gain full control of the affected device, potentially compromising configuration integrity, network security, and service availability.
pion/stun is a Go implementation of STUN. Prior to 3.1.3, XORMappedAddress.GetFromAs can panic while parsing a malformed short XOR-MAPPED-ADDRESS attribute in STUN or ICE Binding-response parsing paths, allowing remote denial of service. This issue is fixed in version 3.1.3.
gemini-bridge is a lightweight MCP server bridging AI agents to Google's Gemini AI via the official CLI. From 1.0.0 until 1.3.1, consult_gemini_with_files in inline mode read any file path supplied in the files argument without confining it to the working directory, then forwarded the contents to the Gemini CLI. Because the caller also controls query, the file contents are echoed back through the Gemini round-trip (and sent to Google), making this an arbitrary local file read. This issue is fixed in version 1.3.1.
WPGraphQL provides a GraphQL API for WordPress sites. From 2.0.0 until 2.15.1, the deprecated user field on SendPasswordResetEmailPayload lets an unauthenticated caller distinguish existing author-class accounts through the sendPasswordResetEmail mutation and obtain public profile fields. This issue is fixed in version 2.15.1.
GeoNetwork is a catalog application to manage spatially referenced resources. From 3.12.0 until 4.2.16 and 4.4.11, unsafe redirect validation in GeonetworkOAuth2LoginAuthenticationFilter and KeycloakAuthenticationProcessingFilter permits an attacker-controlled external redirect after login. This issue is fixed in versions 4.2.16 and 4.4.11.
- https://github.com/geonetwork/core-geonetwork/commit/0d74f673dfc926bde935819ed34636d789b2fecd
- https://github.com/geonetwork/core-geonetwork/commit/cde9b6481a29e2473b7b74479b4e3fd6843bac4e
- https://github.com/geonetwork/core-geonetwork/pull/9307
- https://github.com/geonetwork/core-geonetwork/pull/9309
- https://github.com/geonetwork/core-geonetwork/releases/tag/4.2.16
- https://github.com/geonetwork/core-geonetwork/releases/tag/4.4.11
- https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-pjp7-q6wp-97qx