Comparison Overview
PraderLosinger SA
PraderLosinger SA
Route de Vissigen 110, Sion, 1950, CH
Last Update: 21/12/2025
PraderLosinger opère depuis 1925. Grâce à ses ambassadeurs, jeunes gens du métier et de la maison attachés à des régions spécifiques du Valais, elle répond en connaissance de cause à vos demandes les plus spécifiques. Prenez rendez-vous, exposez vos attentes et nos solu...
AECOM
13355 Noel Road, Dallas, 75240, US
Last Update: 17/09/2026
AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy, transportation and buildings. Our team...
Compliance Ranges Comparison
PraderLosinger SA
AECOM
Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for PraderLosinger SA in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
AECOM has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - PraderLosinger SA (X = Date, Y = Severity)
PraderLosinger SA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AECOM (X = Date, Y = Severity)
AECOM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PraderLosinger SA
AECOM
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.