Comparison Overview
Covestro
Covestro
Friedrich-Ebert Straße 350, Leverkusen, 51373, DE
Last Update: 11/09/2026
Covestro is one of the world’s leading manufacturers of high-quality polymer materials and their components. With its innovative products, processes and methods, the company helps enhance sustainability and the quality of life in many areas. Covestro supplies customers ...
AkzoNobel
Christian Neefestraat 2, Amsterdam, Noord Holland, NL, 1077 WW
Last Update: 16/09/2026
Since 1792, we’ve been supplying the innovative paints and coatings that help to color people’s lives and protect what matters most. Our world class portfolio of brands – including Dulux, International, Sikkens and Interpon – is trusted by customers around the globe. We...
Compliance Ranges Comparison
Covestro
AkzoNobel
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Covestro in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
AkzoNobel has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Covestro (X = Date, Y = Severity)
Covestro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AkzoNobel (X = Date, Y = Severity)
AkzoNobel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Covestro
AkzoNobel
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.