Comparison Overview
Dexcom Lithuania
Dexcom Lithuania
Šeimyniškių g. 19B-501, Vilnius, LT
Last Update: 12/11/2025
Dexcom Lithuania is a Global Business Services Center (GBS): a location for various teams and functions that enables and supports Dexcom's growth. Our teams work in partnership with various departments to streamline processes, innovate with technology and help scale ope...
STERIS
5960 Heisley Rd, Mentor, 44060, US
Last Update: 10/09/2026
STERIS is a leading provider of infection prevention and other procedural products and services, focused primarily on healthcare, pharmaceutical and medical device Customers. MISSION WE HELP OUR CUSTOMERS CREATE A HEALTHIER AND SAFER WORLD by providing innovative healt...
Compliance Ranges Comparison
Dexcom Lithuania
STERIS
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Dexcom Lithuania in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for STERIS in 2026.
Incident History - Dexcom Lithuania (X = Date, Y = Severity)
Dexcom Lithuania cyber incidents detection timeline including parent company and subsidiaries.
Incident History - STERIS (X = Date, Y = Severity)
STERIS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Dexcom Lithuania
STERIS
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.