Comparison Overview
Google Research

Google Research
N/A
Last Update: 11/05/2026
From conducting fundamental research to influencing product development, our research teams have the opportunity to impact technology used by billions of people every day. We aspire to make discoveries that impact everyone, and sharing our research and tools to fuel pr...

OYO
9th Floor, Spaze Palazo,Sourthern Peripheral Road Sector-69, Gurugram, 122001, IN
Last Update: 01/04/2026
OYO is a global platform that aims to empower entrepreneurs and small businesses with hotels and homes by providing full-stack technology products and services that aims to increase revenue and ease operations; bringing easy-to-book, affordable, and trusted accommodatio...
Compliance Ranges Comparison

Google Research







OYO






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Google Research has 268.1% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for OYO in 2026.
Incident History - Google Research (X = Date, Y = Severity)
Google Research cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OYO (X = Date, Y = Severity)
OYO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Google Research

OYO
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.