Comparison Overview
Segue Technologies

Segue Technologies
1515 Wilson Blvd, Arlington, VA, 22209, US
Last Update: 01/01/2026
Segue Technologies is a wholly owned subsidiary of Tetra Tech, Inc. Segue is based out of Arlington, VA, with a presence in 14 states and DC. We support Federal and DoD organizations to develop and enhance mission-critical business systems. We provide custom software ap...

TD SYNNEX North America
5350 Tech Data Dr,, Clearwater, 33760, US
Last Update: 08/09/2026
We’re TD SYNNEX (NYSE: SNX), a leading distributor and solutions aggregator for the IT ecosystem. We’re 22,000 of the IT industry’s best and brightest, who share an unwavering passion for bringing compelling technology products, services and solutions to the world. We’...
Compliance Ranges Comparison

Segue Technologies







TD SYNNEX North America






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Segue Technologies in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for TD SYNNEX North America in 2026.
Incident History - Segue Technologies (X = Date, Y = Severity)
Segue Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TD SYNNEX North America (X = Date, Y = Severity)
TD SYNNEX North America cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Segue Technologies

TD SYNNEX North America
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.