Comparison Overview
Nordstrom

Nordstrom
1600 7th Ave, Seattle, Washington, US, 98101
Last Update: 03/04/2026
At Nordstrom, we empower our employees to set their sights high and blaze their own trails. This is a place where your success and growth are truly a result of your own efforts and achievements. Our teams are made up of motivated people who work hard to become leade...

H&R Block
One H&R Block Way, Kansas City, 64105, US
Last Update: 31/03/2026
H&R Block’s purpose is simple: To provide help and inspire confidence in our clients and communities everywhere. We’ve been true to that purpose since brothers Henry and Richard Bloch founded our company in 1955. Since then, we’ve prepared approximately 800 million tax ...
Compliance Ranges Comparison

Nordstrom







H&R Block






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
Nordstrom has 45.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for H&R Block in 2026.
Incident History - Nordstrom (X = Date, Y = Severity)
Nordstrom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - H&R Block (X = Date, Y = Severity)
H&R Block cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Nordstrom

H&R Block
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.