Comparison Overview
NIPSEA Group I Nippon Paint
NIPSEA Group I Nippon Paint
1 Kim Seng Promenade, Singapore, Singapore, 237994, SG
Last Update: 06/01/2026
NIPSEA Group is a global leader, providing innovative solutions in the paint and coatings industry. Headquartered in Singapore, with 136 NIPSEA companies spread throughout 27 geographical locations, the group is Asia Pacific’s No. 1 paint and coatings manufacturer in bo...
SABIC
PO Box 5101, Riyadh, SA, 11422
Last Update: 17/09/2026
SABIC is a global leader in chemicals headquartered in Riyadh, Saudi Arabia. From making cars and planes more fuel-efficient, to helping conserve the world’s water supply and enabling colorful smartphone cases, we find solutions to the challenges of today to help our cu...
Compliance Ranges Comparison
NIPSEA Group I Nippon Paint
SABIC
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for NIPSEA Group I Nippon Paint in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for SABIC in 2026.
Incident History - NIPSEA Group I Nippon Paint (X = Date, Y = Severity)
NIPSEA Group I Nippon Paint cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SABIC (X = Date, Y = Severity)
SABIC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NIPSEA Group I Nippon Paint
SABIC
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.