Comparison Overview
Nippon Paint Vietnam
Nippon Paint Vietnam
Bien Hoa City, 810000, VN
Last Update: 02/02/2026
Nippon Paint (Vietnam) was established in Vietnam in 1994 as 100% foreign investment equity, located in Bien Hoa Industrial Zone II, Bien Hoa City, Dong Nai Province. Since then, Nippon Paint has become one of top choices among Vietnamese for high quality paint and coat...
Solvay
Rue de Ransbeek 310, Brussels, Belgium, BE, 1120
Last Update: 17/09/2026
For over 160 years, Solvay has been a pioneer in science and innovation, mastering the essential chemistry that powers progress across generations. We are more than a chemical company — we are a catalyst for sustainable transformation, delivering vital solutions that sh...
Compliance Ranges Comparison
Nippon Paint Vietnam
Solvay
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Nippon Paint Vietnam in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Solvay in 2026.
Incident History - Nippon Paint Vietnam (X = Date, Y = Severity)
Nippon Paint Vietnam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Solvay (X = Date, Y = Severity)
Solvay cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nippon Paint Vietnam
Solvay
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.