Comparison Overview
Mannai Corporation QPSC

Mannai Corporation QPSC
PO Box 76, East Industrial St, Building 72, Zone 57 , Doha, undefined, undefined, QA
Last Update: 01/02/2026
Mannai Corporation offers the broadest range of products and services with core activities include automotive and heavy equipment distribution and service, IT, jewelry and luxury goods, retail, home appliances and electronics, travel, engineering services to the oil & g...

Unisys
801 Lakeview Drive, Blue Bell, Pennsylvania, US, 19422
Last Update: 28/03/2026
Unisys is a global technology solutions company that powers breakthroughs for the world’s leading organizations. Our solutions – cloud, AI, digital workplace, logistics and enterprise computing – help our clients challenge the status quo and unlock their full potential....
Compliance Ranges Comparison

Mannai Corporation QPSC







Unisys






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

Mannai Corporation QPSC

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