Comparison Overview
Capgemini Applied Innovation Exchange - San Francisco
Capgemini Applied Innovation Exchange - San Francisco
425 Brannan St, San Francisco, 94107, US
Last Update: 20/03/2026
At the Applied Innovation Exchange, we bring together a dynamic ecosystem of entrepreneurs, emerging technologies, and bold ideas to accelerate sustainable growth for our clients. Our expert team collaborates with the global innovation community to deliver tailored solu...
AeC
Rua Espírito Santo, 871 - Bairro Centro, Belo Horizonte, 30160-031, BR
Last Update: 08/09/2026
A AeC é apontada consistentemente como a líder brasileira na entrega de soluções de experiência do cliente e gestão de processos terceirizados. Servindo as principais marcas do mercado nacional, conquistou nos três últimos anos a posição de Empresa do Ano de BPO pela ...
Compliance Ranges Comparison
Capgemini Applied Innovation Exchange - San Francisco
AeC
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Capgemini Applied Innovation Exchange - San Francisco in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AeC in 2026.
Incident History - Capgemini Applied Innovation Exchange - San Francisco (X = Date, Y = Severity)
Capgemini Applied Innovation Exchange - San Francisco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AeC (X = Date, Y = Severity)
AeC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Capgemini Applied Innovation Exchange - San Francisco
AeC
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.