Comparison Overview
Access Hospitality
Access Hospitality
10 Oakwood Drive, Loughborough, LE11 3QF, GB
Last Update: 04/12/2025
Access Hospitality, part of The Access Group, is redefining the future of hospitality with powerful, end-to-end software built to make venues thrive. Trusted by over 115,000 sites worldwide, our cloud platform connects every corner of your business - from bookings and E...
Bolt
Tallinn, EE
Last Update: 12/09/2026
At Bolt, we're building a future where people don’t need to own personal cars to move around safely and conveniently. A future where people have the freedom to use transport on demand, choosing whatever vehicle's best for each occasion — be it a car, scooter, or e-bike....
Compliance Ranges Comparison
Access Hospitality
Bolt
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Access Hospitality in 2026.
Incidents vs Software Development Industry Avg (This Year)
Bolt has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Access Hospitality (X = Date, Y = Severity)
Access Hospitality cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bolt (X = Date, Y = Severity)
Bolt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Access Hospitality
Bolt
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.