Comparison Overview
NVIDIA Brasil
NVIDIA Brasil
São Paulo, BR
Last Update: 24/04/2026
A invenção da GPU da NVIDIA em 1999 provocou o crescimento do mercado de jogos para PC, redefiniu os gráficos de computador modernos e revolucionou a computação paralela. Mais recentemente, o deep learning com GPU acendeu a AI moderna - a próxima era da computação - com...
Seagate Technology
47488 Kato Rd, Fremont, CA, US, 94538
Last Update: 13/09/2026
Seagate is a leader in mass-capacity data storage. We’ve delivered more than four and a half billion terabytes of capacity over the past four decades. We make storage that scales, bringing trust and integrity to innovations that depend on data. In an era of unprecedente...
Compliance Ranges Comparison
NVIDIA Brasil
Seagate Technology
Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for NVIDIA Brasil in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Seagate Technology in 2026.
Incident History - NVIDIA Brasil (X = Date, Y = Severity)
NVIDIA Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Seagate Technology (X = Date, Y = Severity)
Seagate Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NVIDIA Brasil
Seagate Technology
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.