Comparison Overview
TP-Link Benelux

TP-Link Benelux
Achimedesbaan 18, Nieuwegein, Utrecht, undefined, NL
Last Update: 10/01/2026
Founded in 1996, TP-Link is a global provider of reliable networking devices and smart accessories, involved in all aspects of everyday life. The company is consistently ranked by analyst firm IDC as the No. 1 provider of WLAN and broadband CPE devices*, supplying distr...

JD.COM
JD Building, No. 18 Kechuang 11 Street, BDA, Beijing, 101111, CN
Last Update: 01/08/2026
JD.com, also known as JINGDONG, is a leading e-commerce company transferring to be a technology and service enterprise with supply chain at its core. JD.com’s business has expanded across retail, technology, logistics, health, property development, industrials, and inte...
Compliance Ranges Comparison

TP-Link Benelux







JD.COM






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for TP-Link Benelux in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for JD.COM in 2026.
Incident History - TP-Link Benelux (X = Date, Y = Severity)
TP-Link Benelux cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JD.COM (X = Date, Y = Severity)
JD.COM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TP-Link Benelux

JD.COM
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.