Comparison Overview
Nisga'a Tek, LLC
Nisga'a Tek, LLC
14900 Bogle Dr, Chantilly, Virginia, 20151, US
Last Update: 26/02/2026
Nisga’a Tek is honored to provide services to those who are committed to our national defense, security, and mission. With Nisga’a Tek, your mission is possible, every step of the way – from cybersecurity to mission support to comprehensive intelligence support service...
Globant
875 Howard St, San Francisco, 94103, US
Last Update: 09/09/2026
At Globant, we create the digitally-native products that people love. We bridge the gap between businesses and consumers through technology and creativity, leveraging our experience as an AI powerhouse. We dare to digitally transform organizations and strive to delight ...
Compliance Ranges Comparison
Nisga'a Tek, LLC
Globant
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Nisga'a Tek, LLC in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Globant in 2026.
Incident History - Nisga'a Tek, LLC (X = Date, Y = Severity)
Nisga'a Tek, LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Globant (X = Date, Y = Severity)
Globant cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nisga'a Tek, LLC
Globant
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.