Comparison Overview
IFC Manufacturing
IFC Manufacturing
2121 Pennsylvania Ave NW Washington,, Washington DC, 20433, US
Last Update: 11/01/2026
IFC’s investments in the manufacturing sector boost jobs and promote growth in emerging markets. We work to harness new technologies for development, expand value chains, and support circular economy principles in manufacturing. We focus on developing countries and frag...
Broadridge
605 3rd Ave, 41st Floor, New York, New York, US, 10158
Last Update: 13/09/2026
Broadridge Financial Solutions (NYSE: BR) is a global technology leader with the trusted expertise and transformative technology to help clients and the financial services industry operate, innovate, and grow. We power investing, governance, and communications for our c...
Compliance Ranges Comparison
IFC Manufacturing
Broadridge
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for IFC Manufacturing in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Broadridge in 2026.
Incident History - IFC Manufacturing (X = Date, Y = Severity)
IFC Manufacturing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Broadridge (X = Date, Y = Severity)
Broadridge cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
IFC Manufacturing
Broadridge
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.