Comparison Overview
Manserv

Manserv
Rua Nazaret 369, São Caetano do Sul, BR
Last Update: 03/04/2026
A Manserv tem no ato de servir sua principal vocação. A organização, fundada em 1985, tem estrutura empresarial sólida e abrangente. Especializada nas áreas de Manutenção, Facilities, Logística e Tecnologia, possui extenso portfólio de produtos e serviços, capazes d...

Transguard Group
Emirates Group Security Bldg, Dubai Airport Free Zone, Dubai, 0, AE
Last Update: 02/04/2026
Offering flexible solutions for all of the UAE’s staffing needs since 2001, Transguard Group is the region’s most trusted expert in security, facilities management, cash services and white-collar staffing, and more. With an annual turnover of AED 3.2 billion in FY24/25,...
Compliance Ranges Comparison

Manserv







Transguard Group






Benchmark & Cyber Underwriting Signals
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for Manserv in 2026.
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for Transguard Group in 2026.
Incident History - Manserv (X = Date, Y = Severity)
Manserv cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Transguard Group (X = Date, Y = Severity)
Transguard Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Manserv

Transguard Group
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.