Comparison Overview
Uber Engineering

Uber Engineering
San Francisco, 94103, US
Last Update: 20/03/2026
The Engineering team at Uber builds the technologies that power our platform and reimagines the way the world moves for the better. We thrive on the scale of our global footprint, the gratification of solving hard challenges for millions of users around the world, and b...

Red Hat
100 E. Davie St., Raleigh, NC, US, 27601
Last Update: 19/06/2026
Red Hat is the world’s leading provider of enterprise open source solutions, using a community-powered approach to deliver high-performing Linux, hybrid cloud, edge, and Kubernetes technologies. We hire creative, passionate people who are ready to contribute their idea...
Compliance Ranges Comparison

Uber Engineering







Red Hat






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Uber Engineering in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Red Hat in 2026.
Incident History - Uber Engineering (X = Date, Y = Severity)
Uber Engineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Red Hat (X = Date, Y = Severity)
Red Hat cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Uber Engineering

Red Hat
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.