Comparison Overview
Lumen Public Sector

Lumen Public Sector
Broomfield, 80021, US
Last Update: 07/03/2026
Lumen connects the world. We digitally connect people, data and applications – quickly, securely and effortlessly. Everything we do at Lumen takes advantage of our network strength. From metro connectivity to long-haul data transport to our edge cloud, security, and man...

Tech Mahindra
Erandwane, Pune, Maharashtra, IN, 411004
Last Update: 03/04/2026
Tech Mahindra offers technology consulting and digital solutions to global enterprises across industries, enabling transformative scale at unparalleled speed. With 149k+ professionals across 90+ countries helping 1100+ clients, TechM provides a full spectrum of services...
Compliance Ranges Comparison

Lumen Public Sector







Tech Mahindra






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

Lumen Public Sector

Tech Mahindra
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.