Comparison Overview
Orano Med

Orano Med
700 Klein Road, Plano, TX 75074, US
Last Update: 21/04/2026
Based on an R&D program started in 2005, Orano Med has developed new processes for producing high-purity lead-212 (Pb-212), a rare radioactive isotope. Lead-212 is currently at the heart of promising projects in nuclear medicine to develop new treatments against cancer...

Biocon
Hosur Road, Electronics City, Bangalore, Karnataka, IN, 560100
Last Update: 02/04/2026
Biocon: Enhancing Global Healthcare Biocon Limited, publicly listed in 2004, is India's largest and fully-integrated, innovation-led biopharmaceutical company. It is an emerging global biopharmaceutical enterprise serving customers in over 120 countries. Driven by a...
Compliance Ranges Comparison

Orano Med







Biocon






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

Orano Med

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