Comparison Overview
Ultralytics
Ultralytics
8 Devonshire Square, London, GB, EC2M 4YJ
Last Update: 02/04/2026
Ultralytics is a leading AI company dedicated to creating transformative, open-source computer vision solutions. As creators of YOLO, the world's most popular real-time object detection framework, we empower millions globally—from individual developers to enterprise inn...
1000 W Maude, Sunnyvale, CA, US, 94085
Last Update: 13/09/2026
Founded in 2003, LinkedIn connects the world's professionals to make them more productive and successful. With more than 1 billion members worldwide, including executives from every Fortune 500 company, LinkedIn is the world's largest professional network. The company h...
Compliance Ranges Comparison
Ultralytics
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Ultralytics in 2026.
Incidents vs Software Development Industry Avg (This Year)
LinkedIn has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Ultralytics (X = Date, Y = Severity)
Ultralytics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LinkedIn (X = Date, Y = Severity)
LinkedIn cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ultralytics
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.