Comparison Overview
Zymo Research Corp

Zymo Research Corp
17062 Murphy Ave., None, Irvine, California, US, 92614
Last Update: 08/03/2026
Since its inception in 1994, Zymo Research has been proudly serving the scientific community by providing innovative, reliable, and high quality research tools at affordable prices. Our vision..."The Beauty of Science is to Make Things Simple" is now truer than ever. W...

Amgen
One Amgen Center Drive, Thousand Oaks, CA, US, 91320
Last Update: 31/07/2026
Amgen harnesses the best of biology and technology to fight the world’s toughest diseases, and make people’s lives easier, fuller and longer. We helped establish the biotechnology industry, and we remain on the cutting-edge of innovation, using technology and human gene...
Compliance Ranges Comparison

Zymo Research Corp







Amgen






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Zymo Research Corp in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
Amgen has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Zymo Research Corp (X = Date, Y = Severity)
Zymo Research Corp cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amgen (X = Date, Y = Severity)
Amgen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Zymo Research Corp

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