Comparison Overview
AsyncAPI Initiative
AsyncAPI Initiative
Badajoz, 06008, ES
Last Update: 29/07/2026
We're on a mission to standardize message-based communication and increase interoperability of the different systems available. Help us with AsyncAPI specification and the tooling ecosystem around it. Join our community -> https://www.asyncapi.com/slack-invite/ Press: p...
GoTo Group
Jakarta, ID
Last Update: 12/09/2026
GoTo is the largest technology group in Indonesia, combining on-demand and financial services through the Gojek and GoTo Financial brands. It is the first platform in Southeast Asia to host these two essential use cases in one ecosystem, capturing a majority of Indonesi...
Compliance Ranges Comparison
AsyncAPI Initiative
GoTo Group
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
AsyncAPI Initiative has 86.92% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for GoTo Group in 2026.
Incident History - AsyncAPI Initiative (X = Date, Y = Severity)
AsyncAPI Initiative cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GoTo Group (X = Date, Y = Severity)
GoTo Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AsyncAPI Initiative
GoTo Group
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.