Comparison Overview
Federal Finance Administration
Federal Finance Administration
Bundesgasse 3, Bern, undefined, 3011, CH
Last Update: 13/03/2026
At the Federal Finance Administration, you can expect highly qualified colleagues, an open communication culture, a pleasant working environment and the usual attractive working conditions offered by the Confederation.
Mahindra Group
Worli, Mumbai, 400018, IN
Last Update: 14/09/2026
Many Companies. One Mahindra. Founded in 1945, the Mahindra Group is one of the largest and most admired multinational federations of companies, with 324,000+ employees across 100+ countries. It enjoys a leadership position in farm equipment, utility vehicles, informat...
Compliance Ranges Comparison
Federal Finance Administration
Mahindra Group
Benchmark & Cyber Underwriting Signals
Incidents vs Executive Offices Industry Avg (This Year)
No incidents recorded for Federal Finance Administration in 2026.
Incidents vs Executive Offices Industry Avg (This Year)
No incidents recorded for Mahindra Group in 2026.
Incident History - Federal Finance Administration (X = Date, Y = Severity)
Federal Finance Administration cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mahindra Group (X = Date, Y = Severity)
Mahindra Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Federal Finance Administration
Mahindra Group
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.