Comparison Overview
Extens
Extens
1, Rue de Stockholm, Paris, 75008, FR
Last Update: 29/12/2025
We are a consulting agency in customer experience. Our expertise lies in customer service, customer journey, customer life and customer voice. Emmanuel Richard, the founder and his team work hand in hand with companies to ease the daily lives of customers and employees...
BearingPoint
BearingPoint B.V., Amsterdam, NL-1101 BH, NL
Last Update: 04/09/2026
BearingPoint is an independent management and technology consultancy. Our roots are European, but our footprint is truly global. Transformation is our core service. We deliver value to enterprises, government organizations and NGOs. In a rapidly changing world, Bearing...
Compliance Ranges Comparison
Extens
BearingPoint
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Extens in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for BearingPoint in 2026.
Incident History - Extens (X = Date, Y = Severity)
Extens cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BearingPoint (X = Date, Y = Severity)
BearingPoint cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Extens
BearingPoint
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.