Comparison Overview
Personal
Personal
Calle General Hornos 690, Comuna 1, Ciudad Autónoma de Buenos Aires, AR, 1272
Last Update: 13/09/2026
En Personal, ponemos a las personas en el centro. Somos el ecosistema de servicios de Telecom Argentina S.A. que conecta a cada persona con todo lo que le importa. Nuestra propuesta está pensada para que cada persona, comunidad y organización pueda avanzar, disfrutar y ...
Mynet
I.T.U. Ari Teknokent 2 A Blok, Istanbul, 34469, TR
Last Update: 09/09/2026
Türk internet kullanıcılarının en çok tercih ettiği dijital platform olan Mynet, 1999 yılından bugüne liderliğini koruyor. Kendi alanında sayısız ilki gerçekleştiren öncü internet devi Mynet, Türkiye'nin dijital ekosisteminin kalkınmasına ve gelişmesine destek olmayı sü...
Compliance Ranges Comparison
Personal
Mynet
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Personal in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Mynet in 2026.
Incident History - Personal (X = Date, Y = Severity)
Personal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mynet (X = Date, Y = Severity)
Mynet cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Personal
Mynet
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.