Comparison Overview
Atlas Labs
Atlas Labs
R A De Mel Mawatha, Colombo 3, undefined, undefined, LK
Last Update: 26/02/2026
Atlas labs is a leading technological innovator spanning across multiple industries. With a global clientele that includes leaders in smart cities, construction, aviation and medical research, we consistently challenge ourselves to create products and solutions that del...
Zoom
55 Almaden Blvd., 6th Floor, San Jose, CA 95113, San Jose, 95113, US
Last Update: 10/09/2026
Bring teams together, reimagine workspaces, engage new audiences, and delight your customers –– all on the Zoom AI-first work platform you know and love. 💙 Zoomies help people stay connected so they can get more done together. We set out on a mission to make video com...
Compliance Ranges Comparison
Atlas Labs
Zoom
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Atlas Labs in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Zoom has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - Atlas Labs (X = Date, Y = Severity)
Atlas Labs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zoom (X = Date, Y = Severity)
Zoom cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Atlas Labs
Zoom
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.