Comparison Overview
Infosys Emerging Technology Innovations

Infosys Emerging Technology Innovations
N/A
Last Update: 11/11/2025
iCETS is the emerging technology solution incubation partner for Infosys’ clients and units. We provide next-generation platforms and innovation-as-a-service to future-proof enterprise businesses. The aim is to envision and evolve New Emerging eXploratory Technology (NE...

GFT Technologies
Schelmenwasenstr. 34, Stuttgart, 70567, DE
Last Update: 01/04/2026
GFT Technologies is an AI-centric global digital transformation company. We design advanced data and AI transformation solutions, modernize technology architectures and develop next-generation core systems for industry leaders in Banking, Insurance, Manufacturing and Ro...
Compliance Ranges Comparison

Infosys Emerging Technology Innovations







GFT Technologies






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

Infosys Emerging Technology Innovations

GFT Technologies
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.