Comparison Overview
ETF
ETF
12-14, Rue Louis Blériot, Rueil-Malmaison, Île-de-France, 92500, FR
Last Update: 01/03/2026
Au sein des métiers Réseaux France de VINCI Construction, ETF conçoit, construit et entretient chaque jour les infrastructures ferroviaires nationales, urbaines et privées en France et à travers le monde. Partenaire de vos transports, notre mission est de développer ...
Network Rail
The Quadrant MK, Milton Keynes, MK9 1EN, GB
Last Update: 13/09/2026
We’re at the heart of revitalising Britain’s railway, getting people and goods where they need to be and supporting the economy. Investment and modernisation are essential. So we’re building the railway of the future, running a safe, reliable and efficient railway, and...
Compliance Ranges Comparison
ETF
Network Rail
Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for ETF in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Network Rail in 2026.
Incident History - ETF (X = Date, Y = Severity)
ETF cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Network Rail (X = Date, Y = Severity)
Network Rail cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ETF
Network Rail
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.