Comparison Overview
Nippon Gases Belgium
Nippon Gases Belgium
Metropoolstraat, 17, Schoten, BE, 2900
Last Update: 14/02/2026
Gas. Although you don't always realize it, every second of every single day you are in contact with it. Nippon Gases is able to use something as fundamental as air in ways that make factories cleaner and more productive, food taste better, breathing easier and productio...
BASF
Carl-Bosch-Str. 38, Ludwigshafen, DE, 67056
Last Update: 13/09/2026
At BASF, we create chemistry for a sustainable future. Our ambition: We want to be the preferred chemical company to enable our customers’ green transformation. We combine economic success with environmental protection and social responsibility. Around 112,000 employees...
Compliance Ranges Comparison
Nippon Gases Belgium
BASF
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Nippon Gases Belgium in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
BASF has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Nippon Gases Belgium (X = Date, Y = Severity)
Nippon Gases Belgium cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BASF (X = Date, Y = Severity)
BASF cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nippon Gases Belgium
BASF
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.