Comparison Overview
Tamro Sweden

Tamro Sweden
Importgatan 18, P.O Box 49, Göteborg, Hisings Backa, SE, SE-401 20
Last Update: 16/12/2025
Bakom varje leverans från Tamro finns ett löfte – om trygghet, tillgänglighet och ansvar. Vi rör oss ofta i det tysta, men vårt arbete märks i många människors vardag, varje dag. I över 100 år har vi säkerställt att läkemedel ska finnas där de behövs, när de behövs. Med...

Lupin
3rd Floor, Kalpataru Inspire, Off Western Express Highway, Santa Cruz East, Mumbai, Maharashtra, IN, 400055
Last Update: 12/09/2026
Lupin Limited is a global pharmaceutical leader headquartered in Mumbai, India, with products distributed in over 100 markets. Lupin specializes in pharmaceutical products, including branded and generic formulations, complex generics, biotechnology products, and active ...
Compliance Ranges Comparison

Tamro Sweden







Lupin






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

Tamro Sweden

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