Comparison Overview
Danfoss Brasil

Danfoss Brasil
Osasco, 06273070, BR
Last Update: 28/04/2026
A Danfoss desenvolve soluções que aumentam a produtividade das máquinas, diminuem o consumo de energia, permitem a eletrificação e reduzem as emissões. Nossas soluções são usadas em áreas como refrigeração, ar-condicionado, aquecimento, conversão de energia, controle ...

Rencol Components Ltd.
Unit 2, Avonbridge Trading Estate, Bristol, BS11 9QD, GB
Last Update: 01/04/2026
Following 100 years of successful design and manufacturing experience in plastic and metals, Rencol Components has built a truly global supply chain - rapidly expanding our range of high-quality, competitively-priced industrial components. Rencol has developed a mature...
Compliance Ranges Comparison

Danfoss Brasil







Rencol Components Ltd.






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Danfoss Brasil in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Rencol Components Ltd. in 2026.
Incident History - Danfoss Brasil (X = Date, Y = Severity)
Danfoss Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rencol Components Ltd. (X = Date, Y = Severity)
Rencol Components Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Danfoss Brasil

Rencol Components Ltd.
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.