Comparison Overview
Borouge
Borouge
Sheikh Khalifa Energy Complex, Abu Dhabi, undefined, undefined, AE
Last Update: 13/09/2026
Founded in 1998 through a strategic partnership between ADNOC and Borealis, Borouge was formed to build and operate a petrochemical complex in Al Ruways, United Arab Emirates, with a sales and marketing business in Singapore. Borouge, listed on the Abu Dhabi Securities...
LyondellBasell
LyondellBasell Tower, Ste. 700, 1221 McKinney Street, Houston, TX, US, 77010
Last Update: 13/09/2026
We are LyondellBasell (NYSE: LYB) – a leader in the global chemical industry creating solutions for everyday sustainable living. Through advanced technology and focused investments, we are enabling a circular and low carbon economy. Across all we do, we aim to unlock va...
Compliance Ranges Comparison
Borouge
LyondellBasell
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Borouge in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for LyondellBasell in 2026.
Incident History - Borouge (X = Date, Y = Severity)
Borouge cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LyondellBasell (X = Date, Y = Severity)
LyondellBasell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Borouge
LyondellBasell
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.