Comparison Overview
Philips BioTel Heart
Philips BioTel Heart
1000 Cedar Hollow Rd., Malvern, PA, US, 19355
Last Update: 12/03/2026
CardioNet was just the beginning. Founded on an innovative, patented technology, the result of years of research and development, the company received FDA approval for its core monitoring technology and was the first to provide real-time, heartbeat-by-heartbeat, ECG mon...
Biocon
Hosur Road, Electronics City, Bangalore, Karnataka, IN, 560100
Last Update: 12/09/2026
Biocon: Enhancing Global Healthcare Biocon Limited, publicly listed in 2004, is India's largest and fully-integrated, innovation-led biopharmaceutical company. It is an emerging global biopharmaceutical enterprise serving customers in over 120 countries. Driven by a...
Compliance Ranges Comparison
Philips BioTel Heart
Biocon
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Philips BioTel Heart in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Biocon in 2026.
Incident History - Philips BioTel Heart (X = Date, Y = Severity)
Philips BioTel Heart cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Biocon (X = Date, Y = Severity)
Biocon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Philips BioTel Heart
Biocon
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.