Comparison Overview
iQor

iQor
6700 N. Andrews Ave., Ste. 600 , Fort Lauderdale, FL, US, 33309
Last Update: 02/04/2026
iQor CXBPO™ is a trusted partner in intelligent customer experience solutions for global brands and a portfolio company of Mill Point Capital. With 47,000+ employees across 11 countries, iQor combines three decades of expertise with AI-driven innovation to optimize perf...

VFS Global
Unit 201, Level 2, Gate Village 8, DIFC, P.O. Box 114100, Dubai, AE
Last Update: 16/07/2026
As the global leader in trusted technology services, empowering secure mobility for governments and citizens, VFS Global embraces technological innovation including Generative AI to support governments and diplomatic missions worldwide. VFS Global continuously transform...
Compliance Ranges Comparison

iQor







VFS Global






Benchmark & Cyber Underwriting Signals
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for iQor in 2026.
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
VFS Global has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - iQor (X = Date, Y = Severity)
iQor cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VFS Global (X = Date, Y = Severity)
VFS Global cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

iQor

VFS Global
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.