Comparison Overview
Copart Brasil
Copart Brasil
Rua Henry Ford, 965 - Osasco - SP, Osasco, 06210-108, BR
Last Update: 06/03/2026
Somos a Copart, líder global em leilão de veículos, conectando pessoas a oportunidades há mais de 40 anos. Fundada em 1982 na Califórnia por Willis J. Johnson, a Copart evoluiu de um estabelecimento único para uma gigante do setor, com mais de 200 pátios em países como ...
Ashok Leyland
No.1 Sardar Patel Road, Guindy, Chennai, 600032, IN
Last Update: 10/09/2026
Ashok Leyland vehicles have built a reputation for reliability and ruggedness. The 5,00,000 vehicles we have put on the roads have considerably eased the additional pressure placed on road transportation in independent India. In the populous Indian metros, four out o...
Compliance Ranges Comparison
Copart Brasil
Ashok Leyland
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Copart Brasil in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ashok Leyland in 2026.
Incident History - Copart Brasil (X = Date, Y = Severity)
Copart Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ashok Leyland (X = Date, Y = Severity)
Ashok Leyland cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Copart Brasil
Ashok Leyland
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.