Comparison Overview
Samsung Electronics Polska
Samsung Electronics Polska
Postępu 14, Warszawa, 02-676, PL
Last Update: 24/01/2026
Samsung Electronics Polska to światowy lider w dostarczaniu nowoczesnych technologii cyfrowych wspierających biznes. Nieustannie ulepszamy Digital Signage, kanał sprzedaży profesjonalnych systemów wizualnych dla rozwojowych branż. Oferujemy innowacyjne produkty dynami...
Jabil
10800 Roosevelt Blvd N, St Petersburg, Florida, US, 33716
Last Update: 12/09/2026
At Jabil (NYSE: JBL), we are proud to be a trusted partner for the world's top brands, offering comprehensive engineering, supply chain, and manufacturing solutions. With over 50 years of experience across industries and a vast network of over 100 sites worldwide, Jabil...
Compliance Ranges Comparison
Samsung Electronics Polska
Jabil
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Samsung Electronics Polska in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Jabil in 2026.
Incident History - Samsung Electronics Polska (X = Date, Y = Severity)
Samsung Electronics Polska cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jabil (X = Date, Y = Severity)
Jabil cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Samsung Electronics Polska
Jabil
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.