Comparison Overview
Barclaycard Payments

Barclaycard Payments
1 Churchill Place, Canary Wharf, London, E14 5HP, GB
Last Update: 25/02/2026
Welcome to Barclaycard Payments. We’re leading global payment experts who can help you transform your business – whatever its size, sector or ambition. Barclaycard Payments combines over 50 years of payment experience with insight and data across the Barclays group. ...

Danske Bank
Bernstorffsgade 40, Copenhagen, Capital Region of Denmark, DK, 1577
Last Update: 01/04/2026
Danske Bank – A driver of growth and development For more than a 150 years, Danske Bank has strived to be a driver of growth and development in society. We have developed in tandem with the societies we are part of, and our advisory services, expertise and financial so...
Compliance Ranges Comparison

Barclaycard Payments







Danske Bank






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

Barclaycard Payments

Danske Bank
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.