Comparison Overview
Rudus Oy
Rudus Oy
Karvaamokuja 2a, Helsinki, Uusimaa, 00380, FI
Last Update: 20/11/2025
Rudus on näkyvästi mukana siellä missä rakennetaan: taloja, teitä, siltoja, pihoja... Toimintamme ytimen muodostavat betoni, betonituotteet, erilaiset kiviainekset ja kierrätys. Panostamme rakentamisen laatuun ja kannamme vastuun myös ympäristöstä. Palvelemme Suomen ja ...
Knauf
Am Bahnhof 7, Iphofen, D-97346, DE
Last Update: 08/09/2026
Everyone sees opportunity differently. Knauf sees opportunity in everyone. Similar to other global businesses, our 41,500 team members in 90 countries across 300 sites provide a huge opportunity for anyone with ambition and energy. Unlike other global businesses, you ...
Compliance Ranges Comparison
Rudus Oy
Knauf
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Rudus Oy in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Knauf in 2026.
Incident History - Rudus Oy (X = Date, Y = Severity)
Rudus Oy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Knauf (X = Date, Y = Severity)
Knauf cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Rudus Oy
Knauf
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.