Comparison Overview
Porsche Hungaria
Porsche Hungaria
Fáy utca 27., Budapest, 1139, HU
Last Update: 26/04/2026
Porsche Hungaria Kereskedelmi Kft is a car and auto part wholesale company located in Budapest, Hungary.
Hero MotoCorp
Hero MotoCorp Limited, The Grand Plaza, Plot No.2, Nelson Mandela Road, Vasant Kunj - Phase -II, New Delhi, IN, 110070
Last Update: 13/09/2026
Hero MotoCorp, the world’s largest two-wheeler company, is shaping the future of mobility for over 125 million riders across 48 countries. Our story began in 1984, founded by the visionary Chairman Emeritus, Dr. Brijmohan Lall Munjal, with a bold vision: to make mobilit...
Compliance Ranges Comparison
Porsche Hungaria
Hero MotoCorp
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Porsche Hungaria in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Hero MotoCorp in 2026.
Incident History - Porsche Hungaria (X = Date, Y = Severity)
Porsche Hungaria cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hero MotoCorp (X = Date, Y = Severity)
Hero MotoCorp cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Porsche Hungaria
Hero MotoCorp
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.