Comparison Overview
PPD™ Laboratory Services
PPD™ Laboratory Services
929 N Front St, Wilmington, US
Last Update: 12/03/2026
PPD™ Laboratory Services combines superior scientific expertise with industry-leading technologies supported by a commitment to exceptional quality. Our clients benefit from comprehensive lab services spanning bioanalytical, biomarkers, central lab, GMP and vaccine scie...
Zoetis
10 Sylvan Way, Parsippany, NJ, US, 07054
Last Update: 13/09/2026
The world’s leading animal health company. We’ve been innovating ways to predict, prevent, detect, and treat animal illness for over 70 years, and we continue to stand by those raising and caring for animals worldwide – from veterinarians and pet owners to livestock far...
Compliance Ranges Comparison
PPD™ Laboratory Services
Zoetis
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for PPD™ Laboratory Services in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Zoetis in 2026.
Incident History - PPD™ Laboratory Services (X = Date, Y = Severity)
PPD™ Laboratory Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zoetis (X = Date, Y = Severity)
Zoetis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PPD™ Laboratory Services
Zoetis
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.