Comparison Overview
Capital One

Capital One
1680 Capital One Drive, McLean, 22102, US
Last Update: 01/04/2026
At Capital One, we're making things better for our customers and associates through innovation and collaboration. We were founded on the belief that everyone deserves financial freedom—and are dedicated to a world where all have equal opportunity to prosper. Banking i...

Western Union
7001 E Belleview, Denver, CO, US, 80237
Last Update: 01/04/2026
Many know us as the most trusted way to send money to friends and family overseas and across borders, but we're much more than that. Our talented teams around the world are building new ways to send, save and spend money. Wherever you are in the world, in whatever cur...
Compliance Ranges Comparison

Capital One







Western Union






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

Capital One

Western Union
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.