Comparison Overview
Forvis Mazars in Belgium
Forvis Mazars in Belgium
Marcel Thirylaan 77 - b4, Brussels, undefined, 1200, BE
Last Update: 25/03/2026
Forvis Mazars is a leading provider of audit & assurance, tax, advisory & consulting services worldwide. Operating in over 100 countries and territories, we blend scale, capacity, and coverage with agility, profound insight, and a tailored approach. Our 40,000+ strong...
Citi
388 Greenwich Street, New York, 10013, US
Last Update: 14/09/2026
Citi's mission is to serve as a trusted partner to our clients by responsibly providing financial services that enable growth and economic progress. Our core activities are safeguarding assets, lending money, making payments and accessing the capital markets on behalf o...
Compliance Ranges Comparison
Forvis Mazars in Belgium
Citi
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Forvis Mazars in Belgium in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Citi in 2026.
Incident History - Forvis Mazars in Belgium (X = Date, Y = Severity)
Forvis Mazars in Belgium cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Citi (X = Date, Y = Severity)
Citi cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Forvis Mazars in Belgium
Citi
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.