Comparison Overview
mAdvisor
mAdvisor
One Corporate Place South, 3rd Floor, Piscataway, 08854-6116, US
Last Update: 19/02/2026
mAdvisor employs cognitive technologies like Machine Learning, Machine Reasoning, Natural Language Generation, and Natural Language Processing to simulate human-like behavior to automate intellectual tasks like data analysis, prediction, and forecasting. This enables ke...
AlmavivA Group
Via di Casal Boccone, 188-190, Roma, IT, 00137
Last Update: 11/09/2026
Almaviva is the Italian digital innovation group that supports the country’s growth by helping enterprises meet the challenges of staying competitive in the digital age. The Group helps organizations transform their business models, operational structures, corporate cul...
Compliance Ranges Comparison
mAdvisor
AlmavivA Group
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for mAdvisor in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AlmavivA Group in 2026.
Incident History - mAdvisor (X = Date, Y = Severity)
mAdvisor cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AlmavivA Group (X = Date, Y = Severity)
AlmavivA Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
mAdvisor
AlmavivA Group
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.