Comparison Overview
LGC Mikromol™
LGC Mikromol™
Louis-Pasteur-Straße 30, Luckenwalde, 14943, DE
Last Update: 09/12/2025
At Mikromol we combine an incomparable depth of pharmaceutical knowledge with 25 years of manufacturing experience and scientific acumen to ensure our portfolio of over 5,000 Impurity, Active Pharmaceutical Ingredient (API) and Excipient reference standards is of the hi...
Parexel
541 Church at North Hills St, 1000, Raleigh, North Carolina, US, 27609
Last Update: 12/09/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
LGC Mikromol™
Parexel
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for LGC Mikromol™ in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Parexel in 2026.
Incident History - LGC Mikromol™ (X = Date, Y = Severity)
LGC Mikromol™ 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
LGC Mikromol™
Parexel
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.