Comparison Overview
Blackwoods

Blackwoods
26 Talavera Rd, Macquarie Park, New South Wales, 2113, AU
Last Update: 16/03/2026
Blackwoods is Australia’s leading supplier of industrial and safety supplies. For over 140 years, we have supported businesses big and small with our range of over 300,000 products from the world’s best brands. From the Sydney Harbour Bridge to the most remote corners o...

Grainger
100 Grainger Parkway, Lake Forest, 60045, US
Last Update: 03/04/2026
As a leading business-to-business organization, more than 4.5 million customers worldwide rely on Grainger for products in categories such as safety, material handling and metalworking, along with services like inventory management and technical support. For our Team ...
Compliance Ranges Comparison

Blackwoods







Grainger






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Blackwoods in 2026.
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Grainger in 2026.
Incident History - Blackwoods (X = Date, Y = Severity)
Blackwoods cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Grainger (X = Date, Y = Severity)
Grainger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Blackwoods

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