Comparison Overview
Techcorp Solutions

Techcorp Solutions
Madrid, ES
Last Update: 01/04/2026
Techcorp es una desarrolladora tecnológica que ofrece servicios de consultoría y productos de primer nivel en el plano de la digitalización. Con sede en Madrid, España. Nuestro objetivo es mejorar y aportar soluciones que cambien la forma en la que consumimos contenido ...

Carelon Global Solutions India
Indianapolis, Indianapolis, 46204, US
Last Update: 01/04/2026
Carelon Global Solutions makes healthcare operations more practical, effective, and efficient. Our global team of more than 25K innovators drives growth, delivers exceptional support, and develops digital tools specifically for health plans, providers, and systems. Each...
Compliance Ranges Comparison

Techcorp Solutions







Carelon Global Solutions India






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

Techcorp Solutions

Carelon Global Solutions India
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.