Comparison Overview
JOVI Mobile
JOVI Mobile
N/A
Last Update: 15/05/2026
Olá, somos a JOVI. Uma marca da vivo Mobile Communication Company Limited. Empresa reconhecida globalmente pela inovação e qualidade com mais de 500 milhões de usuários em 60 países. Sucesso no Mundo. Agora no Brasil. Email: [email protected] Telefone: 08000-3...
Openreach
6 Gracechurch Street, London, EC3V 0AT, GB
Last Update: 08/09/2026
We’re the people who make the net work. As the nation’s largest wholesale broadband network, we’re rolling out Ultrafast Full Fibre broadband across the UK. It’s our fastest and most reliable broadband yet, and we’re well on our way to making it available to 25m homes ...
Compliance Ranges Comparison
JOVI Mobile
Openreach
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for JOVI Mobile in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Openreach has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - JOVI Mobile (X = Date, Y = Severity)
JOVI Mobile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Openreach (X = Date, Y = Severity)
Openreach cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
JOVI Mobile
Openreach
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.