Comparison Overview
SERVIER Deutschland GmbH
SERVIER Deutschland GmbH
Elsenheimerstr. 53, None, München, Bayern, DE, 80687
Last Update: 12/02/2026
Servier ist ein privates, global agierendes und forschendes Pharmaunternehmen, das als private Stiftung geführt wird. Gegründet, um uns der Gesundheit und dem Wohl von Patient:innen zu verpflichten, leisten wir einen bedeutenden sozialen und gesellschaftlichen Beitrag s...
Viatris
Pittsburgh, US
Last Update: 13/09/2026
Viatris Inc. (NASDAQ: VTRS) is a global healthcare company uniquely positioned to bridge the traditional divide between generics and brands, combining the best of both to more holistically address healthcare needs globally. With a mission to empower people worldwide to ...
Compliance Ranges Comparison
SERVIER Deutschland GmbH
Viatris
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for SERVIER Deutschland GmbH in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Viatris in 2026.
Incident History - SERVIER Deutschland GmbH (X = Date, Y = Severity)
SERVIER Deutschland GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Viatris (X = Date, Y = Severity)
Viatris cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SERVIER Deutschland GmbH
Viatris
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.