Comparison Overview
UAP Inc.
UAP Inc.
7025 Ontario street East, Montreal, Quebec, H1N 2B3, CA
Last Update: 19/03/2026
UAP is the Canadian leader in the distribution and merchandising of parts and accessories for cars, trucks and heavy vehicles. We employ more than 5,000 individuals who work hard every day to build a recognized and reputable company. UAP is a member of the Genuine Part...
TVS Motor Company
Hosur, Tamil Nadu , Hosur, 635109, IN
Last Update: 13/09/2026
TVS Motor Company is a reputed two and three-wheeler manufacturer globally, championing progress through Mobility with a focus on sustainability. Rooted in our 100-year legacy of Trust, Value, and Passion for Customers and Exactness, we take pride in making internationa...
Compliance Ranges Comparison
UAP Inc.
TVS Motor Company
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for UAP Inc. in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for TVS Motor Company in 2026.
Incident History - UAP Inc. (X = Date, Y = Severity)
UAP Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TVS Motor Company (X = Date, Y = Severity)
TVS Motor Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UAP Inc.
TVS Motor Company
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.