Comparison Overview
Demir Export A.Ş.
Demir Export A.Ş.
İzmir Caddesi 25/7, Ankara, ., 06440, TR
Last Update: 29/11/2025
1957’den beri Türkiye’nin en kaliteli demir cevherini üreten ve sanayiye hammadde sağlayan Demir Export, bugün baz metallerden bakır ve çinko konsantresi ile altın madenciliğinde aktif rol oynamakta. Cevher zenginleştirme, maden üretimi ve dekapaj taahhüt işlerinde y...
Norsk Hydro
Drammensveien 264, Oslo, 0283, NO
Last Update: 10/09/2026
Hydro is a leading industrial company that builds businesses and partnerships for a more sustainable future. We develop industries that matter to people and society. Since 1905, Hydro has turned natural resources into valuable products for people and businesses, creati...
Compliance Ranges Comparison
Demir Export A.Ş.
Norsk Hydro
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Demir Export A.Ş. in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Norsk Hydro in 2026.
Incident History - Demir Export A.Ş. (X = Date, Y = Severity)
Demir Export A.Ş. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Norsk Hydro (X = Date, Y = Severity)
Norsk Hydro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Demir Export A.Ş.
Norsk Hydro
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.