Comparison Overview
AlmavivA Digitaltec
AlmavivA Digitaltec
via F. Lauria Centro Direzionale Isola F8 , 16; 17 ; 18 Piano, Napoli, Campania, IT, 80142
Last Update: 06/03/2026
AlmavivA Digitaltec nasce a fine 2017 per sviluppare attività basate su tecnologie digital e disruptive, strategiche per i clienti AlmavivA. il Gruppo protagonista del processo di digitalizzazione del Paese. L’head quarter della Società è a Napoli, dove lavorano attualm...
Kyndryl
New York City, US
Last Update: 11/09/2026
We have the world’s best talent that design, run, and manage the most advanced and reliable technology infrastructure each day. Together, we think holistically about the health of these vital technology ecosystems. We are a focused, independent company that builds on o...
Compliance Ranges Comparison
AlmavivA Digitaltec
Kyndryl
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AlmavivA Digitaltec in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Kyndryl has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - AlmavivA Digitaltec (X = Date, Y = Severity)
AlmavivA Digitaltec cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kyndryl (X = Date, Y = Severity)
Kyndryl cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AlmavivA Digitaltec
Kyndryl
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.