Comparison Overview
Thorn Lighting

Thorn Lighting
Thorn Lighting Limited, Spennymoor, DL16 6HL, GB
Last Update: 25/02/2026
With nearly 100 years’ experience in manufacturing and supplying efficient, high-quality and connected solutions, Thorn knows lighting, inside out. Our knowledgeable people provide best-in-class support throughout the entire customer journey, while our extensive portfol...

Legrand
128 avenue du Marechal de Lattre de Tassigny, Limoges, FR, 87045
Last Update: 02/04/2026
Legrand is a global specialist in electrical and digital building infrastructures, dedicated to supporting technological, societal and environmental change around the globe. Our purpose is to improve lives by transforming the spaces where people live, work and meet by...
Compliance Ranges Comparison

Thorn Lighting







Legrand






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Thorn Lighting in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Legrand in 2026.
Incident History - Thorn Lighting (X = Date, Y = Severity)
Thorn Lighting cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Legrand (X = Date, Y = Severity)
Legrand cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Thorn Lighting

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