Comparison Overview
gastrodat GmbH
gastrodat GmbH
Karolingerstraße 3/1, Salzburg, 5020, AT
Last Update: 16/04/2026
Simplify your hotel management and relieve your staff with our booking software. Daily recurring tasks determine the image of every tourist accommodation business. The all-in-one hotel software from gastrodat provides everything from a single source: * Hotel software: ...
Meta
1 Hacker Way, Menlo Park, 94025, US
Last Update: 09/09/2026
Meta's mission is to build the future of human connection and the technology that makes it possible. Our technologies help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, In...
Compliance Ranges Comparison
gastrodat GmbH
Meta
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
gastrodat GmbH has 6.54% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Meta has 676.7% more incidents than the average of all companies with at least one recorded incident.
Incident History - gastrodat GmbH (X = Date, Y = Severity)
gastrodat GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Meta (X = Date, Y = Severity)
Meta cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
gastrodat GmbH
Meta
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.