Comparison Overview
Gilead Sciences Germany

Gilead Sciences Germany
Fraunhoferstr. 17, Martinsried , 82152, DE
Last Update: 10/03/2026
Über Gilead Sciences Germany Bei Gilead verfolgen wir seit mehr als 35 Jahren das Unmögliche und wir stecken uns dabei ehrgeizige Ziele. Unsere Mission: die Welt für alle Menschen zu einem gesünderen Ort machen. Deshalb entwickeln und vertreiben wir innovative Arzneimit...

Agilent Technologies
5301 Stevens Creek Boulevard, Santa Clara, 95051, US
Last Update: 01/04/2026
Agilent customers are finding new ways to treat cancer, ensure food, water, air, and medicine quality and safety, discover new drug treatments, research infectious diseases, and create alternative energy solutions for a greener planet. From start to finish, we have them...
Compliance Ranges Comparison

Gilead Sciences Germany







Agilent Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Gilead Sciences Germany in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Agilent Technologies in 2026.
Incident History - Gilead Sciences Germany (X = Date, Y = Severity)
Gilead Sciences Germany cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Agilent Technologies (X = Date, Y = Severity)
Agilent Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Gilead Sciences Germany

Agilent Technologies
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.