Comparison Overview
Independent and Community Pharmacy

Independent and Community Pharmacy
6555 State Hwy 161 , Irving, TX, 75039, US
Last Update: 21/04/2026
For Health Marts and other independent pharmacies, we host McKesson ideaShare - the leading conference designed to help independent pharmacy owners and their staff improve their knowledge, performance and profitability. Attend to share ideas, ask questions and gather ...

Parexel
541 Church at North Hills St, 1000, Raleigh, North Carolina, US, 27609
Last Update: 03/04/2026
Parexel is a leading global clinical research organization (CRO) providing insights-driven Clinical and Consulting solutions to the world’s life sciences industry. Leveraging deep local knowledge and a global breadth of clinical, regulatory and therapeutic expertise, ou...
Compliance Ranges Comparison

Independent and Community Pharmacy







Parexel






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Independent and Community Pharmacy in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Parexel in 2026.
Incident History - Independent and Community Pharmacy (X = Date, Y = Severity)
Independent and Community Pharmacy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Parexel (X = Date, Y = Severity)
Parexel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Independent and Community Pharmacy

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