Comparison Overview
Porsche Macedonia
Porsche Macedonia
бул. Босна и Херцеговина 4, Скопје, 1000, MK
Last Update: 01/04/2026
Порше Македонија е компанија која ги застапува автомобилските брендови Volkswagen, Audi, Škoda, SEAT, Porsche и Volkswagen комерцијални возила. Присутна на македонскиот пазар од крајот на 2005 година, таа е единствениот импортер во државата во директна сопственост на пр...
Cummins Inc.
500 Jackson St, Columbus, 47201, US
Last Update: 13/09/2026
At Cummins, we empower everyone to grow their careers through meaningful work, building inclusive and equitable teams, coaching, development and opportunities to make a difference. Across our entire organization, you'll find engineers, developers, and technicians who ar...
Compliance Ranges Comparison
Porsche Macedonia
Cummins Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Porsche Macedonia in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Cummins Inc. in 2026.
Incident History - Porsche Macedonia (X = Date, Y = Severity)
Porsche Macedonia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cummins Inc. (X = Date, Y = Severity)
Cummins Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Porsche Macedonia
Cummins Inc.
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.