Comparison Overview
One Workplace
One Workplace
2500 De La Cruz Boulevard, None, Santa Clara, California, US, 95050
Last Update: 09/03/2026
We create spaces that inspire and transform. One Workplace doesn’t just create spaces, we put them to work. We don’t measure them in square feet, but by the possibilities they create for our clients. From a better way to express your culture, to a better way to work, ...
Dar
Beirut, LB
Last Update: 01/04/2026
Dar is one of the world’s leading consultancies, providing design, planning, engineering, sustainability consulting, digital solutions and services, project management, and facilities management for buildings, cities, transportation, civil infrastructure, water, and the...
Compliance Ranges Comparison
One Workplace
Dar
Benchmark & Cyber Underwriting Signals
Incidents vs Design Services Industry Avg (This Year)
No incidents recorded for One Workplace in 2026.
Incidents vs Design Services Industry Avg (This Year)
No incidents recorded for Dar in 2026.
Incident History - One Workplace (X = Date, Y = Severity)
One Workplace cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dar (X = Date, Y = Severity)
Dar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
One Workplace
Dar
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.