Comparison Overview
Tekniska högskolan vid Linköpings universitet
Tekniska högskolan vid Linköpings universitet
Mäster Mattias väg 8, Linköping, 581 83, SE
Last Update: 02/02/2026
Tekniska högskolan vid Linköpings universitet är en av Sveriges stora tekniska högskolor, med ca 14 800 studenter och mer än 1 000 anställda. Med campus i Linköping, Norrköping och på Lidingö utbildar vi ingenjörer, fysiker, kemister, biologer, matematiker, datavetare,...
EF
Selnaustrasse 30, Zurich, 8001, CH
Last Update: 13/09/2026
Founded in 1965 in Sweden, EF (Education First) is a global association of education companies that shares a common mission of opening the world through education, offering language, academic, cultural exchange and education travel programs. Some companies are in the ...
Compliance Ranges Comparison
Tekniska högskolan vid Linköpings universitet
EF
Benchmark & Cyber Underwriting Signals
Incidents vs Education Industry Avg (This Year)
No incidents recorded for Tekniska högskolan vid Linköpings universitet in 2026.
Incidents vs Education Industry Avg (This Year)
No incidents recorded for EF in 2026.
Incident History - Tekniska högskolan vid Linköpings universitet (X = Date, Y = Severity)
Tekniska högskolan vid Linköpings universitet cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EF (X = Date, Y = Severity)
EF cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tekniska högskolan vid Linköpings universitet
EF
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.