Comparison Overview
Pinnacle Enterprise Holdings Ltd

Pinnacle Enterprise Holdings Ltd
N/A
Last Update: 13/03/2026
Pinnacle Enterprise Holdings Limited is a Hong Kong based B2B internet technology company focusing on research and develop online game and its related products and services. The company is established in early 2015 by a group of industrial experts who have 10+ years of ...

Nagarro
Munich, DE
Last Update: 31/03/2026
Nagarro helps future-proof your business through a forward-thinking, fluidic, and CARING mindset. We excel at digital engineering and help our clients become human-centric, digital-first organizations, augmenting their ability to be responsive, efficient, intimate, crea...
Compliance Ranges Comparison

Pinnacle Enterprise Holdings Ltd







Nagarro






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

Pinnacle Enterprise Holdings Ltd

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