Comparison Overview
BNP Paribas Personal Finance

BNP Paribas Personal Finance
141 Rue Anatole France, Levallois-Perret, IdF, FR, 92300
Last Update: 02/04/2026
BNP Paribas Personal Finance is a major player in consumer credit in France and Europe, offering a wide range of consumer lending products. A 100% subsidiary of the BNP Paribas Group, the company provides, through its brands Cetelem, Findomestic, and Alpha Credit, a com...

ING
Bijlmerdreef 106, Amsterdam, North Holland, NL, 1102 CT
Last Update: 01/04/2026
ING is a pioneer in digital banking and on the forefront as one of the most innovative banks in the world. As ING, we have a clear purpose that represents our conviction of people’s potential. We don’t judge, coach, or tell people how to live their lives. However big or...
Compliance Ranges Comparison

BNP Paribas Personal Finance







ING






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas Personal Finance in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING in 2026.
Incident History - BNP Paribas Personal Finance (X = Date, Y = Severity)
BNP Paribas Personal Finance cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ING (X = Date, Y = Severity)
ING cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BNP Paribas Personal Finance

ING
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.