Comparison Overview
Zeppelin Equipment Norway
Zeppelin Equipment Norway
Bølerveien 60, Skedsmokorset, Akershus, NO, 2020
Last Update: 21/03/2026
Zeppelin Construction Equipment Norway AS er forhandler av Cat anleggsmaskiner på det norske markedet. Vi selger nye og brukte maskiner samt driver utleie av anleggsmaskiner og utstyr gjennom vårt søsterselskap, Zeppelin Rental. Vi tilbyr landsdekkende service med over ...
STRABAG
Ortenburger Strasse 27, Spittal/Drau, 9800, AT
Last Update: 15/09/2026
At STRABAG around 86,000 people working on progress at more than 2,400 locations worldwide. Uniqueness and individual strengths characterise both our projects and each of us as individuals. Whether its building construction, civil engineering, road construction, undergr...
Compliance Ranges Comparison
Zeppelin Equipment Norway
STRABAG
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Zeppelin Equipment Norway in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for STRABAG in 2026.
Incident History - Zeppelin Equipment Norway (X = Date, Y = Severity)
Zeppelin Equipment Norway cyber incidents detection timeline including parent company and subsidiaries.
Incident History - STRABAG (X = Date, Y = Severity)
STRABAG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Zeppelin Equipment Norway
STRABAG
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.