Comparison Overview
AVENIR CONSEIL
AVENIR CONSEIL
65, Avenue Édouard Vaillant, Boulogne-Billancourt, Île-de-France, 92100, FR
Last Update: 26/02/2026
Produits complexes, processus optimisés, usines intelligentes : Comment maitriser et exploiter les données ? Avenir Conseil est le spécialiste du déploiement des SI métiers et de l’accompagnement des organisations. Nous mettons notre savoir-faire et notre expérience au...
FIS
601 Riverside Ave, Jacksonville, 32202, US
Last Update: 14/09/2026
Unlocking financial technology. Bringing the world’s money into harmony. At FIS, we advance the way the world pays, banks, and invests. With decades of expertise, we provide financial technology solutions to financial institutions, businesses, and developers. Headquart...
Compliance Ranges Comparison
AVENIR CONSEIL
FIS
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AVENIR CONSEIL in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for FIS in 2026.
Incident History - AVENIR CONSEIL (X = Date, Y = Severity)
AVENIR CONSEIL cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FIS (X = Date, Y = Severity)
FIS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AVENIR CONSEIL
FIS
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.