Comparison Overview
Inetum Consulting
Inetum Consulting
7, Rue Touzet Gaillard, St.-Ouen, 93400, FR
Last Update: 25/02/2026
Inetum Consulting is a strategy and transformation consulting firm. With a team of 450 multidisciplinary consultants, we are present in Europe (France, Spain, Portugal, Belgium) and Africa (Morocco). Inetum Consulting supports companies and public organizations in their...
Ayesa
Parque Científico Tecnológico Cartuja, Sevilla, Andalucía 41092, ES, Sevilla, Sevilla, ES
Last Update: 05/04/2026
Ayesa is a global provider of technology and engineering services with more than 11500 employees in twenty-three countries across Europe, Latin America, Africa and Asia. The company develops and implements digital solutions for the private and public sector and uses the...
Compliance Ranges Comparison
Inetum Consulting
Ayesa
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Inetum Consulting in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Ayesa in 2026.
Incident History - Inetum Consulting (X = Date, Y = Severity)
Inetum Consulting cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ayesa (X = Date, Y = Severity)
Ayesa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Inetum Consulting
Ayesa
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.