Comparison Overview
TP-Link UK Limited

TP-Link UK Limited
144 Cardiff Road, Reading, Berkshire, RG1 8EW, GB
Last Update: 21/04/2026
For the last 12 consecutive years research firm IDC has identified TP-Link as the worlds Number 1 wireless manufacturer. Committed to powerful R&D, effective production and strict quality management, TP-Link continues to develop award-winning networking products in Wire...

Infosys
Infosys Limited, Bangalore, Karnataka, IN, 560100
Last Update: 07/05/2026
Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over three decades of experience in managing the systems and workings of global enterprises, we expe...
Compliance Ranges Comparison

TP-Link UK Limited







Infosys






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for TP-Link UK Limited in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys in 2026.
Incident History - TP-Link UK Limited (X = Date, Y = Severity)
TP-Link UK Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Infosys (X = Date, Y = Severity)
Infosys cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TP-Link UK Limited

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