Comparison Overview
Liberty IT
Liberty IT
Adelaide Exchange, 24-26 Adelaide Street, Belfast, Co Antrim, GB, BT2 8GD
Last Update: 01/04/2026
We’re a bunch of inventors, problem solvers, business brains and tech transformers. We revel in a challenge and stop at nothing to provide the solution, exceeding expectations, breaking new ground and transforming customer interactions. With over 25 years’ experience w...
Upwork
475 Brannan St, San Francisco, 94107, US
Last Update: 12/09/2026
Upwork is the world’s work marketplace that connects businesses with independent talent from across the globe. We serve everyone from one-person startups to large, Fortune 100 enterprises with a powerful, trust-driven platform that enables companies and talent to work t...
Compliance Ranges Comparison
Liberty IT
Upwork
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Liberty IT in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Upwork in 2026.
Incident History - Liberty IT (X = Date, Y = Severity)
Liberty IT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Upwork (X = Date, Y = Severity)
Upwork cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Liberty IT
Upwork
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.