Comparison Overview
KPMG Business Expérience
KPMG Business Expérience
2, Avenue Gambetta, Courbevoie, 92400, FR
Last Update: 17/03/2026
Notre engagement : fournir des solutions expertes, innovantes et sur mesure pour surmonter vos défis les plus exigeants, répondre à vos besoins complexes et interconnectés. KPMG en France s'appuie sur un large éventail de domaines d'expertise, dont l'audit, la fiscalit...
XP Inc.
Avenida Chedid Jafet 75, Torre sul 30º andar, São Paulo, São Paulo, BR, 04551-065
Last Update: 07/09/2026
A XP Inc. é uma das maiores instituições financeiras independente do Brasil, dona das marcas XP, Rico, Clear, XP Educação, InfoMoney, entre outras. Com mais de 4,8 milhões de clientes ativos e um valor superior a R$ 2,1 trilhão de ativos sob custódia, há 25 anos vem tra...
Compliance Ranges Comparison
KPMG Business Expérience
XP Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for KPMG Business Expérience in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for XP Inc. in 2026.
Incident History - KPMG Business Expérience (X = Date, Y = Severity)
KPMG Business Expérience cyber incidents detection timeline including parent company and subsidiaries.
Incident History - XP Inc. (X = Date, Y = Severity)
XP Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
KPMG Business Expérience
XP Inc.
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.