Comparison Overview
Intertek Brazil
Intertek Brazil
Alameda Mamoré, Barueri, São Paulo, 06454-040, BR
Last Update: 16/01/2026
For more than 130 years, companies around the world have depended on Intertek to help ensure the quality and safety of their products, processes and systems. We go beyond testing, inspecting and certifying products; we are a Total Quality Assurance provider to industri...
The World Bank
1818 H Street, NW, Washington, DC, US, 20433
Last Update: 14/09/2026
The World Bank is a vital source of financial and technical assistance to developing countries around the world. Our vision is to create a world free of poverty on a livable planet. We are not a bank in the common sense; we are made up of two unique development institu...
Compliance Ranges Comparison
Intertek Brazil
The World Bank
Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Intertek Brazil in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for The World Bank in 2026.
Incident History - Intertek Brazil (X = Date, Y = Severity)
Intertek Brazil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The World Bank (X = Date, Y = Severity)
The World Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Intertek Brazil
The World Bank
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.