Comparison Overview
LinkedIn Design
LinkedIn Design
900 W Maude Ave, Sunnyvale, 94085, US
Last Update: 05/12/2025
Our LinkedIn Design team is made up of over 270 passionate makers. We are product designers, user researchers, content designers, communication designers, and operational experts. We work on a wide range of products, from global consumer apps, and enterprise products fo...
Jumia Group
109 Adeniyi Jones, Ikeja , 1234, NG
Last Update: 12/09/2026
Jumia (NYSE :JMIA) is a leading e-commerce platform in Africa. It is built around a marketplace, Jumia Logistics, and JumiaPay. The marketplace helps millions of consumers and sellers to connect and transact. Jumia Logistics enables the delivery of millions of packages ...
Compliance Ranges Comparison
LinkedIn Design
Jumia Group
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for LinkedIn Design in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Jumia Group in 2026.
Incident History - LinkedIn Design (X = Date, Y = Severity)
LinkedIn Design cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jumia Group (X = Date, Y = Severity)
Jumia Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
LinkedIn Design
Jumia Group
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.