Comparison Overview
EltaMD Skin Care
EltaMD Skin Care
N/A
Last Update: 10/11/2025
At EltaMD, we make professional sun and skin care that’s trusted by Dermatologists and loved by skin. In fact, Dermatologists don’t just recommend EltaMD, they personally use our sunscreens more than any other professional sun care brand. We’ve spent over 30 years deve...
SUN PHARMA
Sun House, CTS No. 201 B/1,, Mumbai, 400063, IN
Last Update: 12/09/2026
Sun Pharma is the world's fourth-largest speciality generic pharmaceutical company and No. 1 in India. We provide high-quality, affordable medicines trusted by customers and patients in over 100 countries. Sun Pharma's global presence is supported by more than 40 manufa...
Compliance Ranges Comparison
EltaMD Skin Care
SUN PHARMA
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for EltaMD Skin Care in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for SUN PHARMA in 2026.
Incident History - EltaMD Skin Care (X = Date, Y = Severity)
EltaMD Skin Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SUN PHARMA (X = Date, Y = Severity)
SUN PHARMA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
EltaMD Skin Care
SUN PHARMA
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.