Comparison Overview
Danieli Culture

Danieli Culture
Via Nazionale, 41, Buttrio, 33042, IT
Last Update: 08/09/2026
Danieli Culture is where we share the business culture of the Danieli Group — our people, our vision, our technologies, our choices, and the real-world impact we create every day. It's a culture built on sustainable innovation, operational excellence, talent development...

SKF Group
Sven Wingquist Gata 2, Göteborg, SE-415 50, SE
Last Update: 12/09/2026
We fight friction to move the world forward. 20% of all energy consumed is spent overcoming friction. At SKF, we’re constantly fighting that friction, to reduce energy waste and make the most of the resources we have. Since 1907, we’ve been making some of the world’...
Compliance Ranges Comparison

Danieli Culture







SKF Group






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Danieli Culture in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for SKF Group in 2026.
Incident History - Danieli Culture (X = Date, Y = Severity)
Danieli Culture cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SKF Group (X = Date, Y = Severity)
SKF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Danieli Culture

SKF 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.