Comparison Overview
BNP Paribas Factor Nordics

BNP Paribas Factor Nordics
Adelgade 12, 1, 1123 Copenhagen, Copenhagen, 1123, DK
Last Update: 27/12/2025
"The oxygen in your growth story" The right working capital at the right time. With a customized plan, you get the support you need. We can help you grow your business by: - Pre-financing your invoices, allowing you to maintain good cash flow - Credit insurance against ...

HSBC
8 Canada Square, London, E14 5HQ, GB
Last Update: 27/07/2026
Opening up a world of opportunity for our customers, investors, ourselves and the planet. We're a financial services organisation that serves more than 40 million customers, ranging from individual savers and investors to some of the world’s biggest companies and gover...
Compliance Ranges Comparison

BNP Paribas Factor Nordics







HSBC






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

BNP Paribas Factor Nordics

HSBC
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.